The tap outputs a schema that includes fields that are not selected in the catalog. This has a couple of unwanted effects:
- 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
- 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.