-
Notifications
You must be signed in to change notification settings - Fork 161
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
Use branch 8007-contract_type_aliasing #954
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-bigquery contributing guide. |
@@ -13,12 +13,9 @@ | |||
@dataclass(init=False) | |||
class BigQueryColumn(Column): | |||
TYPE_LABELS = { | |||
"STRING": "STRING", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we just be adding TEXT
? Why delete the other types?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no point to types that are the same on both sides. They do nothing except (in some cases) change the type from lowercase to uppercase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed them in the dbt-core PR because they were causing unnecessary churning in the test cases.
The test is currently failing because in test_constraints.py the "integer" type is being translated to "int64". It looks like the tests were working before with "integer". Is that conversion not necessary? |
resolves #953
Problem
Need to match changes in dbt-labs/dbt-core#8592
Solution
Fix the test. Add TEXT => STRING conversion to TYPE_LABELS.
Checklist