-
Notifications
You must be signed in to change notification settings - Fork 38
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 evolution error when denormalized
and snake_case
is enabled
#66
Comments
denormalized
is enableddenormalized
and snake_case
is enabled
Alright so it looks like in my specific case the issue is caused because the mut_schema being a concatenation of For double word column names, an underscore is introduced so we'll just end up having a duplicated column (e.,g. That's when we end up with the following error, regardless of the sink since the |
I am experiencing the same issue. The Denormalized class calls
Would a solution be to replace this line with:
The former is the actual scheme as requested from bigquery table, the second is the internal representation of the table applying appropriate transforms. |
I'm running into issues to load data with the denormalised parameter enabled.
Looking into the code, it seems that even when the table does not yet exists in BigQuery, we run into the following error:
The table schema is properly defined in BigQuery, but when it comes to load the actual data it looks like the table schema if not resolved correctly. The issue persists with both version 1 and 2 of the
schema_resolver
. Maybe there is an issue with the schema_translator?If someone has Salesforce credentials, here is the corresponding Meltano configuration for reproducing the issue:
And the
meltano
commands:The text was updated successfully, but these errors were encountered: