Skip to content
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

Schema includes fields that are not selected for sync #47

Open
dobesv opened this issue Dec 24, 2019 · 0 comments
Open

Schema includes fields that are not selected for sync #47

dobesv opened this issue Dec 24, 2019 · 0 comments

Comments

@dobesv
Copy link

dobesv commented Dec 24, 2019

The tap outputs a schema that includes fields that are not selected in the catalog. This has a couple of unwanted effects:

  1. If the target cares about the schema (MySQL, BigQuery, Parquet, etc.) this will result in the creation of columns that will never have a value set in them
  2. If the target doesn't support some type output by the stripe tap, disabling that field cannot be used to avoid an error in the target. For example, SQL doesn't really allow a field to be a string OR an object, but the Stripe schema includes fields with that type. Sending the Stripe schema to such a target results in an error that is not easy to remedy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant