Skip to content

fix(databricks): emit only changed column-tag keys in SET TAGS diffs - #16275

Draft
sd-db wants to merge 2 commits into
dbt-labs:mainfrom
sd-db:sd-db/port/1668-column-tags-keys
Draft

sd-db wants to merge 2 commits into
dbt-labs:mainfrom
sd-db:sd-db/port/1668-column-tags-keys

Conversation

@sd-db

@sd-db sd-db commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Port dbt-databricks#1668: for a column whose tags changed, ALTER COLUMN … SET TAGS now includes only new or updated keys, not that column's full desired map.
  • Unchanged columns are still omitted. Newly tagged columns still receive the full desired map.
  • Set-only semantics are unchanged: remote-only keys are never unset.
  • Follow-up to #16247, which skips unchanged columns but still sends the full map for a changed column.

Fixes #16272

Test plan

  • cargo test -p dbt-adapter test_get_diff_ (including test_get_diff_omits_unchanged_keys_within_column)
  • CI on this PR

Match dbt-databricks#1668: skip unchanged columns and, for a changed column, send only new or updated keys. SET TAGS remains apply-only.
@cla-bot cla-bot Bot added the cla:yes label Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Databricks] Emit only changed column-tag keys in SET TAGS diffs

1 participant