<?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: Hive Metastore End of Life in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136162#M50504</link>
    <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/194630"&gt;@julius_bkr&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;There are no plans to deactivate the Hive Metastore. May I ask where you found that information? It seems to me that the Hive Metastore will be supported for many years. For example, Microsoft doesn’t support UC in GovCloud.&lt;BR /&gt;Plus, a lot of customers still have huge amounts of legacy pipelines that rely on the Hive Metastore.&lt;BR /&gt;&lt;BR /&gt;So you can rest easy &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 27 Oct 2025 10:17:48 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2025-10-27T10:17:48Z</dc:date>
    <item>
      <title>Hive Metastore End of Life</title>
      <link>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136152#M50501</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;is there a rough date on which the Hive Metastore will be deactivated?&lt;/P&gt;&lt;P&gt;In the end, I ask the question again, which was already asked 2 years ago:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.databricks.com/t5/data-engineering/hive-metastore-table-access-control-end-of-support/td-p/50487" target="_blank" rel="noopener"&gt;Solved: Hive metastore table access control End of Support - Databricks Community - 50487&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Weve got many scripts that use hive metastore and are trying to plan our migration to unity catalog.&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2025 09:33:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136152#M50501</guid>
      <dc:creator>julius_bkr</dc:creator>
      <dc:date>2025-10-27T09:33:56Z</dc:date>
    </item>
    <item>
      <title>Re: Hive Metastore End of Life</title>
      <link>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136162#M50504</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/194630"&gt;@julius_bkr&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;There are no plans to deactivate the Hive Metastore. May I ask where you found that information? It seems to me that the Hive Metastore will be supported for many years. For example, Microsoft doesn’t support UC in GovCloud.&lt;BR /&gt;Plus, a lot of customers still have huge amounts of legacy pipelines that rely on the Hive Metastore.&lt;BR /&gt;&lt;BR /&gt;So you can rest easy &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2025 10:17:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136162#M50504</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2025-10-27T10:17:48Z</dc:date>
    </item>
    <item>
      <title>Re: Hive Metastore End of Life</title>
      <link>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136164#M50505</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/194630"&gt;@julius_bkr&lt;/a&gt;&amp;nbsp;I do not think Databricks has any plans to retire HMA completely. However,&amp;nbsp;Unity Catalog is the strategic direction and the recommended approach for new deployments and migrating existing data governance. Databricks is investing heavily in Unity Catalog and continually adding features to it. So it would be better to migrate to UC. Without UC, you are just using the bare minimum features of Databricks, and to be able to execute advanced use cases including GenAI, and/or feature like Genie, DLT, Lakehouse Federation, Delta sharing, Cleanrooms etc. you should migrate to UC at the earliest.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2025 10:49:55 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136164#M50505</guid>
      <dc:creator>Abhishek_Patel</dc:creator>
      <dc:date>2025-10-27T10:49:55Z</dc:date>
    </item>
    <item>
      <title>Re: Hive Metastore End of Life</title>
      <link>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136165#M50506</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/110502"&gt;@szymon_dybczak&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks for you reply :). That's a reassuring answer. Maybe I concluded too early that this will happen at some point. The explicit marking with "Legacy" in databricks makes this effect for me. The docs (&lt;A href="https://docs.databricks.com/aws/en/database-objects/hive-metastore#gsc.tab=0" target="_blank"&gt;Database objects in the legacy Hive metastore | Databricks on AWS&lt;/A&gt;) state "... &lt;SPAN&gt;data governance using&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Hive metastore&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;is deprecated. Databricks recommends that you use&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Unity Catalog ..."&lt;/SPAN&gt;, which could indicate this for me + the label "Legacy".&lt;/P&gt;</description>
      <pubDate>Mon, 27 Oct 2025 10:54:08 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/hive-metastore-end-of-life/m-p/136165#M50506</guid>
      <dc:creator>julius_bkr</dc:creator>
      <dc:date>2025-10-27T10:54:08Z</dc:date>
    </item>
  </channel>
</rss>

