-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix for nullable top-level schemas #44401
Fix for nullable top-level schemas #44401
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
You'll need to bump the connector version & docs too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
blegh. if you have an easy way to test - what happens if the top-level schema is type: [string, object]
? (we've seen that in the past also)
@edgao we would not be able to handle that in avro anyway. What would the top-level string field be called? The field names come from the object properties. |
154e7ff
to
77c1f9d
Compare
/publish-java-cdk
|
/publish-java-cdk
|
9fec536
to
500d2e0
Compare
/publish-java-cdk
|
/publish-java-cdk force=true
|
/publish-java-cdk force=true
|
What
Bugfix for https://github.com/airbytehq/oncall/issues/6269