-
Notifications
You must be signed in to change notification settings - Fork 403
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
[Fix] type issue in databricks_sql_table
#4422
base: main
Are you sure you want to change the base?
Conversation
…ore then one word in a string
databricks_sql_table
databricks_sql_table
You also need to think how to handle cases like, if you have a decimal type declared as |
I used regex instead. I looked at this document and it seems all the types use parentheses to signify arguments. |
Integration tests has failed with the following error:
|
I updated the template generation to include the needed delta flag |
@alexott Anything else I can do? |
It looks like there is some syntax error - integration tests are failing with:
|
🤦♂️ just updated. |
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.
in general looks good, but need to think on how the change of the type may affect apply/read (I'm not sure if it won't lead to the configuration drift).
integration test is passing, but we need to fix our build to make it overall green
return caseInsensitiveColumnType | ||
return normalizedColumnType |
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'm not sure about this change, need to think how changes like decimal(12, 2)
-> decimal(12,2)
will affect the plan/apply and then read operations
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.
Yeah, let me know what you think the best approach is and I'm happy to implement.
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
Changes
Updated type check to only compare the first word in the type string.
Tests
make test
run locallydocs/
folderinternal/acceptance