🎉 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 }})

tuliren

What

How

Pre-merge Checklist (Updating a connector)

Community member or Airbyter

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

@tuliren tuliren temporarily deployed to more-secrets

October 22, 2021 20:42

Inactive

@tuliren tuliren changed the titleSupport additional properties in json schema 🎉 Destination S3 & GCS: support additional properties

Oct 22, 2021

@tuliren tuliren temporarily deployed to more-secrets

October 22, 2021 21:54

Inactive

@tuliren tuliren temporarily deployed to more-secrets

October 22, 2021 23:12

Inactive

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 08:26

Inactive

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 10:25

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

October 23, 2021 10:27

Inactive

@tuliren

Contributor Author

tuliren commented

Oct 23, 2021

edited by github-actionsbot

Loading

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 10:41

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

October 23, 2021 10:42

Inactive

@tuliren

Contributor Author

tuliren commented

Oct 23, 2021

edited by github-actionsbot

Loading

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 10:45

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

October 23, 2021 10:47

Inactive

@tuliren tuliren marked this pull request as ready for review

October 23, 2021 11:11

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 11:12

Inactive

tuliren

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 11:15

Inactive

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 15:21

Inactive

@tuliren

Contributor Author

tuliren commented

Oct 23, 2021

edited by github-actionsbot

Loading

@tuliren

Contributor Author

tuliren commented

Oct 23, 2021

edited by github-actionsbot

Loading

@tuliren tuliren temporarily deployed to more-secrets

October 23, 2021 19:34

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

October 23, 2021 19:35

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

October 23, 2021 19:35

Inactive

sherifnada

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 tuliren temporarily deployed to more-secrets

November 3, 2021 08:16

Inactive

@tuliren

@tuliren tuliren temporarily deployed to more-secrets

November 3, 2021 08:50

Inactive

@tuliren

@tuliren tuliren temporarily deployed to more-secrets

November 3, 2021 09:06

Inactive

@tuliren

@tuliren tuliren temporarily deployed to more-secrets

November 3, 2021 09:08

Inactive

@tuliren

@tuliren

Contributor Author

tuliren commented

Nov 3, 2021

edited by github-actionsbot

Loading

@tuliren

Contributor Author

tuliren commented

Nov 3, 2021

edited by github-actionsbot

Loading

@tuliren

Confirmed in a local deployment that the new Json Avro converter can properly handle S3 source with additional properties.

@jrhizor jrhizor temporarily deployed to more-secrets

November 3, 2021 09:23

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

November 3, 2021 09:23

Inactive

@tuliren

@tuliren

Contributor Author

tuliren commented

Nov 3, 2021

edited by github-actionsbot

Loading

@tuliren

Contributor Author

tuliren commented

Nov 3, 2021

edited by github-actionsbot

Loading

@jrhizor jrhizor temporarily deployed to more-secrets

November 3, 2021 15:46

Inactive

@jrhizor jrhizor temporarily deployed to more-secrets

November 3, 2021 15:46

Inactive

@tuliren

@tuliren tuliren temporarily deployed to more-secrets

November 3, 2021 17:14

Inactive

@tuliren

@tuliren tuliren temporarily deployed to more-secrets

November 3, 2021 17:18

Inactive

@tuliren tuliren deleted the liren/patch-avro-schema-converter branch

November 3, 2021 18:37

@tuliren tuliren linked an issue

Nov 4, 2021

that may beclosed by this pull request

schlattk pushed a commit to schlattk/airbyte that referenced this pull request

Jan 4, 2022

@tuliren @schlattk