I’m using the Connector Builder (Airbyte 0.44.5) to build a low-code connector. The when an object is occasionally null, the schema detection will produce a specification like this:

"some_object": {
      "anyOf": [
        {
          "type": "null"
        },
        {
          "properties": {
            "id": {
              "type": "integer"
            },
            "name": {
              "type": "string"
            }
          },
          "type": "object"
        }
      ]
    }

as opposed to when there are no nulls, it will produce:

"some_object": {
      "properties": {
        "id": {
          "type": "integer"
        },
        "name": {
          "type": "string"
        }
      },
      "type": "object"
    }

The second is correctly recognized as an object, while the first is classed as Unknown which prevents it being synced. I can’t tell if this comment is highlighting the same issue: https://github.com/airbytehq/airbyte/issues/25669#issuecomment-1559850741

A message from kapa.ai

@kapa.ai Is this required for the field to be nullable?

A message from kapa.ai

Hi Gabriel, we are about to ship a fix for this. Should be deployed sometime this week on cloud, perhaps early next week for OSS

@Gabriel Levine Here is the PR Sherif is referencing in case you want to follow along: https://github.com/airbytehq/airbyte/pull/26741