🎉 Destination S3 & GCS: support additional properties by tuliren · Pull Request #7288 · airbytehq/airbyte (original) (raw)
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 andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation22 Commits19 Checks0 Files changed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
[ Show hidden characters]({{ revealButtonHref }})
What
How
- Use patched Json / Avro converter from https://github.com/airbytehq/json-avro-converter.
Recommended reading order
- Schema conversion:
JsonToAvroSchemaConverter.java
- Schema and object conversion test cases:
json_conversion_test_cases.json
- The rest
Pre-merge Checklist (Updating a connector)
Community member or Airbyter
- Grant edit access to maintainers (instructions)
- Secrets in the connector's spec are annotated with
airbyte_secret
- Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
. - Code reviews completed
- Documentation updated
- Connector's
README.md
- Connector's
bootstrap.md
. See description and examples - Changelog updated in
docs/integrations/<source or destination>/<name>.md
including changelog. See changelog example
- Connector's
- PR name follows PR naming conventions
- Connector version bumped like described here
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
- Create a non-forked branch based on this PR and test the below items on it
- Build is successful
- Credentials added to Github CI. Instructions.
- /test connector=connectors/ command is passing.
- New Connector version released on Dockerhub by running the
/publish
command described here
tuliren temporarily deployed to more-secrets
Inactive
tuliren changed the titleSupport additional properties in json schema 🎉 Destination S3 & GCS: support additional properties
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
tuliren temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
tuliren temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
tuliren marked this pull request as ready for review
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
tuliren temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
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
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!
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
Confirmed in a local deployment that the new Json Avro converter can properly handle S3 source with additional properties.
jrhizor temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
- Bump version once the connectors are published.
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
Contributor Author
tuliren commented
•
edited by github-actionsbot
Loading
jrhizor temporarily deployed to more-secrets
Inactive
jrhizor temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren temporarily deployed to more-secrets
Inactive
tuliren deleted the liren/patch-avro-schema-converter branch
tuliren linked an issue
that may beclosed by this pull request
schlattk pushed a commit to schlattk/airbyte that referenced this pull request
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