-
Notifications
You must be signed in to change notification settings - Fork 153
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
[Bug] New RANGE type in bigquery failing when setting descriptions #1341
Labels
Comments
borjavb
changed the title
[Bug] New RANGE type in bigquery not working when setting descriptions
[Bug] New RANGE type in bigquery failing when setting descriptions
Sep 11, 2024
Hey, @borjavb. I was interested in this and took a quick look. Seems to work for me based on some cursory playing around. Are you able to confirm what version of A few observations:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a new bug in dbt-bigquery?
Current Behavior
When using the new RANGE type, in a model, the model will be created correctly, but dbt will fail while trying to update the descriptions of the schema:
400 PATCH <> Range field <field> must have a range element type.
The new SchemaField for RANGE data types expects an extra parameter
range_element_type
with values {date,datetime,timestamp} in order to work https://cloud.google.com/python/docs/reference/bigquery/latest/google.cloud.bigquery.schema.SchemaFieldExpected Behavior
dbt runs correctly and applies the column descriptions without erroring
Steps To Reproduce
Create a model with its respective yaml file description, and run it
table_a.sql
table_a.yaml
Relevant log output
400 PATCH <> Range field column_range must have a range element type.
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: