<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Question about which tags appear in drop down in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/question-about-which-tags-appear-in-drop-down/m-p/121147#M46355</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/165414"&gt;@andreapeterson&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, your understanding of Databricks tag behavior is correct. In Databricks Unity Catalog, tags follow a hierarchical inheritance pattern:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Downward inheritance&lt;/STRONG&gt;: Tags applied at higher levels (catalog → schema → table) become available in the dropdown menus for lower levels. This allows you to easily apply organizational or governance tags consistently across related assets.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Column-level isolation&lt;/STRONG&gt;: Tags created at the column level don't automatically propagate to other columns' dropdown menus.&lt;BR /&gt;This is by design to prevent dropdown clutter from highly specific, single-use column tags.&lt;BR /&gt;This behavior makes sense in Databricks' governance model because:&lt;BR /&gt;- &lt;STRONG&gt;Catalog-level tags&lt;/STRONG&gt; are typically for broad organizational categories (like "PII", "Finance", "Marketing")&lt;BR /&gt;- &lt;STRONG&gt;Schema-level tags&lt;/STRONG&gt; might represent departmental or project-specific classifications&lt;BR /&gt;- &lt;STRONG&gt;Table-level tags&lt;/STRONG&gt; could indicate data types or processing stages&lt;BR /&gt;- &lt;STRONG&gt;Column-level tags&lt;/STRONG&gt; are usually very specific descriptors that don't need to be reused elsewhere&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Workaround for frequently used column tags:&lt;/STRONG&gt; If you find yourself repeatedly typing the same column-level tag, you can:&lt;BR /&gt;- Apply it at a higher level first (table/schema) to make it available in dropdowns&lt;BR /&gt;- Use it on columns as needed&lt;BR /&gt;- Optionally remove it from the higher level later if it's not actually applicable there&lt;/P&gt;&lt;P&gt;This hierarchical approach aligns with Databricks' emphasis on data governance and helps maintain clean,&lt;BR /&gt;organized tagging without overwhelming users with irrelevant options in their dropdown menus.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jun 2025 16:13:06 GMT</pubDate>
    <dc:creator>lingareddy_Alva</dc:creator>
    <dc:date>2025-06-06T16:13:06Z</dc:date>
    <item>
      <title>Question about which tags appear in drop down</title>
      <link>https://community.databricks.com/t5/data-engineering/question-about-which-tags-appear-in-drop-down/m-p/121141#M46352</link>
      <description>&lt;P&gt;Hi there, I have a question regarding the appearance of tags in the drop down when adding a tag to a resource (catalog, schema, table, column - level). When does a tag get populated in a drop down? I noticed when I created a column level tag, and wanted to apply it to the next column, it wouldn't populate in the drop down and I had to keep retyping. However, if a tag is place on something higher up in the hierarchy (catalog,schema, or table level) , that tag would then populate in anything lower than its hierarchy i.e. the columns tag drop down.&lt;BR /&gt;&lt;BR /&gt;Is this logic correct?&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jun 2025 15:10:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/question-about-which-tags-appear-in-drop-down/m-p/121141#M46352</guid>
      <dc:creator>andreapeterson</dc:creator>
      <dc:date>2025-06-06T15:10:28Z</dc:date>
    </item>
    <item>
      <title>Re: Question about which tags appear in drop down</title>
      <link>https://community.databricks.com/t5/data-engineering/question-about-which-tags-appear-in-drop-down/m-p/121147#M46355</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/165414"&gt;@andreapeterson&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, your understanding of Databricks tag behavior is correct. In Databricks Unity Catalog, tags follow a hierarchical inheritance pattern:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Downward inheritance&lt;/STRONG&gt;: Tags applied at higher levels (catalog → schema → table) become available in the dropdown menus for lower levels. This allows you to easily apply organizational or governance tags consistently across related assets.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Column-level isolation&lt;/STRONG&gt;: Tags created at the column level don't automatically propagate to other columns' dropdown menus.&lt;BR /&gt;This is by design to prevent dropdown clutter from highly specific, single-use column tags.&lt;BR /&gt;This behavior makes sense in Databricks' governance model because:&lt;BR /&gt;- &lt;STRONG&gt;Catalog-level tags&lt;/STRONG&gt; are typically for broad organizational categories (like "PII", "Finance", "Marketing")&lt;BR /&gt;- &lt;STRONG&gt;Schema-level tags&lt;/STRONG&gt; might represent departmental or project-specific classifications&lt;BR /&gt;- &lt;STRONG&gt;Table-level tags&lt;/STRONG&gt; could indicate data types or processing stages&lt;BR /&gt;- &lt;STRONG&gt;Column-level tags&lt;/STRONG&gt; are usually very specific descriptors that don't need to be reused elsewhere&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Workaround for frequently used column tags:&lt;/STRONG&gt; If you find yourself repeatedly typing the same column-level tag, you can:&lt;BR /&gt;- Apply it at a higher level first (table/schema) to make it available in dropdowns&lt;BR /&gt;- Use it on columns as needed&lt;BR /&gt;- Optionally remove it from the higher level later if it's not actually applicable there&lt;/P&gt;&lt;P&gt;This hierarchical approach aligns with Databricks' emphasis on data governance and helps maintain clean,&lt;BR /&gt;organized tagging without overwhelming users with irrelevant options in their dropdown menus.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jun 2025 16:13:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/question-about-which-tags-appear-in-drop-down/m-p/121147#M46355</guid>
      <dc:creator>lingareddy_Alva</dc:creator>
      <dc:date>2025-06-06T16:13:06Z</dc:date>
    </item>
  </channel>
</rss>

