-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Destination BigQuery: map "airbyte_type": "big_number" to BIGNUMERIC #12658
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
Comments
As datatype mapping for destiantion-bigquery should be done on the normalization side, I'm moving this ticket to the board of Phyton team |
notes from grooming: in the new protocol that supports annotations for data types, this will not be needed. Likely can close this after Destination BigQuery and normalization are updated to handle new protocol version |
Basically should be closed along the way once this PR is merged #19721 |
merged into the feature branch |
Due to new updates in the building of JSON schema, a new property
"airbyte_type"
was added to the field description.One of the possible values for
"airbyte_type"
is"big_number"
. Now"airbyte_type"
is ignored and all"big_number"
fields are mapped as"STRING"
in destination BigQuery.According to #11090 and this comment all fields with
"airbyte_type": "big_number"
should be mapped asBIGNUMERIC
in destination BigQuery.Input JSON schema example:
Input data example:
The text was updated successfully, but these errors were encountered: