<?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: Legacy hive_metatstore corruption in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126871#M47790</link>
    <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/177273"&gt;@thbeh_com&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, this is a fairly common issue during UC migrations, especially with legacy Hive metastore tables. The corruption typically happens because:&lt;BR /&gt;- Metadata-data misalignment - Hive metastore references files that no longer exist or have been moved&lt;BR /&gt;- Parquet schema evolution issues - Column changes not properly reflected in metastore&lt;BR /&gt;- Concurrent operations during migration causing inconsistent states&lt;BR /&gt;- File system operations bypassing Hive metastore updates&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 29 Jul 2025 23:47:42 GMT</pubDate>
    <dc:creator>lingareddy_Alva</dc:creator>
    <dc:date>2025-07-29T23:47:42Z</dc:date>
    <item>
      <title>Legacy hive_metatstore corruption</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126870#M47789</link>
      <description>&lt;P&gt;I am seeing some legacy hive_metastore corruption (especially tables created as parquet instead of Delta) lately in my client's place, who is in the midst of migrating to UC. We were provided with a Scala code to remove the erroneous Parquet files physically. Anyone facing a similar issue?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 23:21:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126870#M47789</guid>
      <dc:creator>thbeh_com</dc:creator>
      <dc:date>2025-07-29T23:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy hive_metatstore corruption</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126871#M47790</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/177273"&gt;@thbeh_com&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, this is a fairly common issue during UC migrations, especially with legacy Hive metastore tables. The corruption typically happens because:&lt;BR /&gt;- Metadata-data misalignment - Hive metastore references files that no longer exist or have been moved&lt;BR /&gt;- Parquet schema evolution issues - Column changes not properly reflected in metastore&lt;BR /&gt;- Concurrent operations during migration causing inconsistent states&lt;BR /&gt;- File system operations bypassing Hive metastore updates&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Jul 2025 23:47:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126871#M47790</guid>
      <dc:creator>lingareddy_Alva</dc:creator>
      <dc:date>2025-07-29T23:47:42Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy hive_metatstore corruption</title>
      <link>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126872#M47791</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/24053"&gt;@lingareddy_Alva&lt;/a&gt;. Your points very much reflect the current situation.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jul 2025 00:05:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/legacy-hive-metatstore-corruption/m-p/126872#M47791</guid>
      <dc:creator>thbeh_com</dc:creator>
      <dc:date>2025-07-30T00:05:59Z</dc:date>
    </item>
  </channel>
</rss>

