You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
resource"databricks_sql_table""system_views" {
for_each=local.views_wkscatalog_name=local.catalog_nameschema_name=each.value.schemaname=each.value.tableowner=each.value.ownertable_type="VIEW"view_definition=format(<<-EOF SELECT * FROM system.%s.%s WHERE workspace_id IN (%s) EOF
,
each.value.schema, each.value.table,
join(", ", each.value.workspaces_id)
)
properties={
"delta.mergeSchema"="true"
}
depends_on=[databricks_schema.system_schemas]
}
Expected Behavior
The property delta.mergeSchema should remain true when set explicitly, ensuring that schema changes are handled seamlessly in Databricks views without Terraform attempting to reset the property.
Actual Behavior
When delta.mergeSchema is set to true to handle schema changes, Terraform defaults this property to false. During the next terraform apply, Terraform attempts to set delta.mergeSchema back to true, causing the operation to fail.
Steps to Reproduce
Configure a Databricks view with delta.mergeSchema set to true.
Apply the configuration with Terraform.
Observe that Terraform reverts the property to false.
On subsequent terraform apply, Terraform attempts to reset the property to true, resulting in a failure.
Terraform and provider versions
databricks = {
source = "databricks/databricks"
version = "1.53.0"
}
Is it a regression?
This behavior has not been observed to work in previous versions of the provider.
Important Factoids
This behavior causes disruptions in environments where schema evolution needs to be managed dynamically.
The text was updated successfully, but these errors were encountered:
alexott
changed the title
[ISSUE] Issue with databricks_XXX resource
[ISSUE] Issue with databricks_sql_table resource
Nov 15, 2024
Configuration
Expected Behavior
The property delta.mergeSchema should remain true when set explicitly, ensuring that schema changes are handled seamlessly in Databricks views without Terraform attempting to reset the property.
Actual Behavior
When delta.mergeSchema is set to true to handle schema changes, Terraform defaults this property to false. During the next terraform apply, Terraform attempts to set delta.mergeSchema back to true, causing the operation to fail.
Steps to Reproduce
Terraform and provider versions
databricks = {
source = "databricks/databricks"
version = "1.53.0"
}
Is it a regression?
This behavior has not been observed to work in previous versions of the provider.
Important Factoids
This behavior causes disruptions in environments where schema evolution needs to be managed dynamically.
The text was updated successfully, but these errors were encountered: