feat: support key-only databricks_tags#1339
feat: support key-only databricks_tags#1339canbekley wants to merge 9 commits intodatabricks:1.12.latestfrom
Conversation
Signed-off-by: Can Bekleyici <can.bekleyici@deepl.com>
Signed-off-by: Can Bekleyici <can.bekleyici@deepl.com>
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||
|
Hi @canbekley — thanks a lot for driving this one, and apologies for the delay on our side. Quick heads-up: this is a quarterly priority for our team and I'm looking to land it this week. If you have bandwidth to continue, please let me know. Otherwise, I can drive the change to completion — I'll push the remaining fixes directly to your branch so your commits stay and you remain co-author on anything I add. Please let me know either way when you get a chance. |
|
hi @sd-db , thank you for your thorough review! I can commit the suggested changes later today and let you know. |
|
hi @sd-db , I applied your suggestions. can you check again please? |
- Add `null_value:` (bare key, YAML parses to None) alongside the existing empty-string case in the column-tags functional fixtures. This matches the exact input form reported in databricks#1270 and exercises the `None -> ""` coercion end-to-end. - CHANGELOG: fix "settings" typo and mention that `None` is also accepted as an input form for key-only tags. Co-authored-by: Can Bekleyici <can.bekleyici@deepl.com>
|
Pushed two small follow-ups directly to the branch (
|
|
I have also rebased this to |
Resolves #1270
Description
Provides a solution to add support for configuring key-only
databricks_tagsfor tables and columns. Utilizes existing databricks sql patterns, which treat values of key-only patterns as empty strings (when queried frominformation_schema.tagsand also when applied via sql:ALTER TABLE ... SET TAGS ('key_only_tag' = '', ...))Checklist
CHANGELOG.mdand added information about my change to the "dbt-databricks next" section.