-
Notifications
You must be signed in to change notification settings - Fork 353
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
[ISSUE] Issue with databricks_sql_table
resource
#3490
Comments
@ollimandoliini, if you write However in my project we now have the issue of type definitions like this : It looks like the provider is getting column definitions from the backend without the additional information regarding Identity settings. Passing the type-string in as above with |
Thanks, that made the plan succeed! I was thinking it must be something like this. There also seems to be an issue with type synonyms. If you define a column with type |
@ollimandoliini, yes from my understanding Databricks translates some types in "popular naming" into internal types. Same with |
Configuration
Expected Behavior
A previously created SQL table should work normally when running
plan
/apply
/destroy
.Actual Behavior
When running
plan
/apply
/destroy
with unchanged configuration for a previously created table, the command will fail with an error:Steps to Reproduce
Terraform and provider versions
Terraform v1.8.1
on linux_amd64
Is it a regression?
I don't know
Debug Output
Important Factoids
The first and only mention of the error in debug logs:
Would you like to implement a fix?
No.
The text was updated successfully, but these errors were encountered: