<?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: Glue Catalog Metadata Management with Enforced Tagging in Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/96573#M39297</link>
    <description>&lt;P&gt;You can use lakeFS pre-merge hooks to force this. Works great with this stack -&amp;gt;&amp;nbsp;&lt;A href="https://lakefs.io/blog/lakefs-hooks/" target="_blank"&gt;https://lakefs.io/blog/lakefs-hooks/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Oct 2024 20:48:51 GMT</pubDate>
    <dc:creator>145676</dc:creator>
    <dc:date>2024-10-28T20:48:51Z</dc:date>
    <item>
      <title>Glue Catalog Metadata Management with Enforced Tagging in Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/94319#M38867</link>
      <description>&lt;DIV class=""&gt;&lt;P&gt;As part of the data governance team, we're trying to enforce table-level tagging when users create tables in a Databricks environment where metadata is managed by AWS Glue Catalog (non-Unity Catalog). Is there a way to require tagging at table creation, or to set up a process that enforces tagging in such an environment? Any guidance on best practices or tools to implement this would be appreciated&lt;/P&gt;&lt;/DIV&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 16 Oct 2024 17:01:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/94319#M38867</guid>
      <dc:creator>KartRasi_10779</dc:creator>
      <dc:date>2024-10-16T17:01:56Z</dc:date>
    </item>
    <item>
      <title>Re: Glue Catalog Metadata Management with Enforced Tagging in Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/95752#M39167</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/1337"&gt;@KartRasi_10779&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;How are you doing today?&lt;/P&gt;&lt;P&gt;As per my understanding,&amp;nbsp;Consider &lt;STRONG&gt;creating a tagging enforcement process&lt;/STRONG&gt; by implementing a custom script or trigger that checks for table tags post-creation, as AWS Glue Catalog doesn't natively support mandatory tagging at table creation. You could use &lt;STRONG&gt;AWS Lambda&lt;/STRONG&gt; functions combined with &lt;STRONG&gt;Glue triggers&lt;/STRONG&gt; to monitor for new table creation and automatically apply or validate tags. Another approach is to integrate &lt;STRONG&gt;Databricks jobs&lt;/STRONG&gt; that run periodically to ensure all tables have the required tags and alert when tags are missing. Best practices would include setting up clear tagging policies and using &lt;STRONG&gt;automation tools&lt;/STRONG&gt; like &lt;STRONG&gt;Databricks REST API&lt;/STRONG&gt; or &lt;STRONG&gt;Glue Crawlers&lt;/STRONG&gt; to ensure tags are consistently applied across all tables.&lt;/P&gt;&lt;P&gt;Give a try and let me know the outcome.&lt;/P&gt;&lt;P&gt;Hoping you have a good day.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Brahma&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 16:02:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/95752#M39167</guid>
      <dc:creator>Brahmareddy</dc:creator>
      <dc:date>2024-10-23T16:02:04Z</dc:date>
    </item>
    <item>
      <title>Re: Glue Catalog Metadata Management with Enforced Tagging in Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/96573#M39297</link>
      <description>&lt;P&gt;You can use lakeFS pre-merge hooks to force this. Works great with this stack -&amp;gt;&amp;nbsp;&lt;A href="https://lakefs.io/blog/lakefs-hooks/" target="_blank"&gt;https://lakefs.io/blog/lakefs-hooks/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Oct 2024 20:48:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/glue-catalog-metadata-management-with-enforced-tagging-in/m-p/96573#M39297</guid>
      <dc:creator>145676</dc:creator>
      <dc:date>2024-10-28T20:48:51Z</dc:date>
    </item>
  </channel>
</rss>

