fix: apply column-level tags for V1 table materialization#1346
Open
fix: apply column-level tags for V1 table materialization#1346
Conversation
The V1 table materialization path was missing the apply_column_tags() call, causing column-level databricks_tags to be silently ignored for tables while working correctly for views.
benc-db
approved these changes
Mar 9, 2026
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
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.
Summary
databricks_tagswere silently ignored for tables using the V1 (default) materialization pathapply_column_tags()call that the view, V2 table, streaming table, and materialized view materializations all haveTest plan
TestColumnTagsTableV1— Added V1-specific functional testTestColumnTagsTableV2— confirms V2 path is unaffected,TestColumnTagsViewV1— confirms views still work correctly