-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
🎉 Destination S3 & GCS: support additional properties #7288
Conversation
e2f0772
to
083e240
Compare
/test connector=connectors/destination-s3
|
/test connector=connectors/destination-gcs
|
.../destination-s3/src/main/java/io/airbyte/integrations/destination/s3/avro/AvroConstants.java
Outdated
Show resolved
Hide resolved
/test connector=connectors/destination-s3
|
/test connector=connectors/destination-gcs
|
} | ||
] | ||
}, |
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.
if I'm reading this file correctly, the json schema doesn't actually need to have additionalProperties=true
for this column to be added/handled correctly, is that right? That seems like a good idea because it makes it resilient to undocumented/unannounced schema changes
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.
Right. Most schemas do not specify additionalProperties=true
and many of them include additional fields anyway. Eventually, I think we should handle all invalid cases. The S3 destination does not judge. It only hoards!
.../destination-s3/src/main/java/io/airbyte/integrations/destination/s3/avro/AvroConstants.java
Outdated
Show resolved
Hide resolved
241bb5b
to
74457e8
Compare
/test connector=connectors/destination-s3
|
/test connector=connectors/destination-gcs
|
Confirmed in a local deployment that the new Json Avro converter can properly handle S3 source with additional properties. |
|
/publish connector=connectors/destination-s3
|
/publish connector=connectors/destination-gcs
|
* Log json schema * Use patched json avro converter * Rename schema * Update unit test cases * Fix ab ap field schema conversion * Rename files * Add unit test cases * Fix dependency for databricks * Bump versions * Update documentations * Update gcs doc * Set additional properties field name * Revert s3 and gcs version * Specify extra props fields * Refactor json avro conversion doc * Update connector doc * Fix databricks spec typo * Bump connector versions in seed
What
How
Recommended reading order
JsonToAvroSchemaConverter.java
json_conversion_test_cases.json
Pre-merge Checklist (Updating a connector)
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing./publish
command described here