docs(databricks): merge databricks_tags additively across config hierarchy levels#9379
Merged
Merged
Conversation
…archy levels (databricks/dbt-databricks#1340) `databricks_tags` now merges additively across dbt config hierarchy levels: a model-level `databricks_tags` value no longer clobbers tags defined at the project level — instead the dictionaries are merged (child keys override matching parent keys, other parent keys are retained). This is a breaking change for projects that relied on lower-level configs fully replacing higher-level ones.
|
@sd-db is attempting to deploy a commit to the dbt-labs Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
luna-bianca
reviewed
Jun 17, 2026
luna-bianca
left a comment
luna-bianca
left a comment
Contributor
There was a problem hiding this comment.
Thanks for opening this PR, @sd-db ! I have some editorial suggestions, please check! Also, can you please add this update to Upgrade guide for 1.12? Thanks!
Co-authored-by: Bianca Luna <biancacamille.luna@dbtlabs.com>
luna-bianca
approved these changes
Jun 18, 2026
Contributor
|
Hey @sd-db , I went ahead and pushed the changes + approved/merged the PR. I'll open a new PR to add this update to the Upgrade guide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does
Documents that
databricks_tagsnow merges additively across dbt config hierarchy levels as of dbt-databricks v1.12.0. Previously, a lower-level config (e.g. model-level) fully replaced a higher-level one (e.g. project-level); now the dictionaries are merged — keys defined at the lower level override matching keys from the higher level, and any other higher-level keys are retained.This documents the behavior change introduced in databricks/dbt-databricks#1340.
Changes
databricks_tagssection.databricks_tagsis set — tables, columns, materialized views, and streaming tables.Which audience does this affect?
dbt-databricks users on v1.12.0+ who set
databricks_tagsat more than one config hierarchy level.