-
Notifications
You must be signed in to change notification settings - Fork 456
Open
Description
Configuration
resource "databricks_sql_table" "example_table" {
name = local.example_table_name
catalog_name = var.example_catalog.name
schema_name = example_catalog.example_schema.name
table_type = "MANAGED"
warehouse_id = data.databricks_sql_warehouse.warehouse.id
comment = "Example resource"
owner = var.resource_owner_name
properties = {
"delta.feature.allowColumnDefaults" = "supported"
}
column {
name = "column_a"
type = "STRING"
comment = ""
nullable = false
}
column {
name = "column_b"
type = "TIMESTAMP DEFAULT current_timestamp()"
comment = ""
nullable = false
}
}
Expected Behavior
When I apply the first time the table is created successfully. When I plan/apply a second time with the same configuration no changes should be detected.
Actual Behavior
When I apply the first time the table is created successfully. However, a follow up plan/apply will yield the error changing the 'type' of an existing column is not supported
.
Steps to Reproduce
terraform version
Terraform v1.10.4
on darwin_arm64
+ provider registry.terraform.io/databricks/databricks v1.63.0
Is it a regression?
Nope
Debug Output
Important Factoids
Would you like to implement a fix?
Maybe if I have time
apamildner, k-scherer and svyotov-lg
Metadata
Metadata
Assignees
Labels
No labels