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
Source S3: choose between data types when merging master schema #16631
Source S3: choose between data types when merging master schema #16631
Conversation
…ring merging json schemas
/test connector=connectors/source-s3
Build PassedTest summary info:
|
/publish connector=connectors/source-s3
if you have connectors that successfully published but failed definition generation, follow step 4 here |
…ytehq#16631) * airbytehq#422 source s3: choose broadest data type when there is a mismatch during merging json schemas * airbytehq#422 source s3: upd changelog
…ytehq#16631) * airbytehq#422 source s3: choose broadest data type when there is a mismatch during merging json schemas * airbytehq#422 source s3: upd changelog
What
When master schema is constructed of two or more json schemas, it is possible there is a type mismatch. In this case we log a warning and the type remains what it was in a user provided configuration. If user did not fill in the schema, an error is raised.
How
If possible - try to choose the broadest of two datatypes. Otherwise, do what we used to do - raise an error