<?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: Read Snowflake Iceberg tables from Databricks UC in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/read-snowflake-iceberg-tables-from-databricks-uc/m-p/126932#M47805</link>
    <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143355"&gt;@jeanptello&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;It’s possible that there’s a mismatch between what Snowflake has written and what Databricks is trying to read. This often happens if Snowflake has performed an operation that rewrites the table files (like compaction or a bulk update), and then Databricks tries to validate an older version that no longer matches the current state.&lt;/P&gt;&lt;P class=""&gt;I’d recommend:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Refreshing the table from Databricks&lt;/STRONG&gt;&lt;/SPAN&gt; to ensure it’s accessing the most recent version.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Checking the table history in both Snowflake and Databricks&lt;/STRONG&gt;&lt;/SPAN&gt; to verify whether both systems are seeing the same snapshot, or if there’s a discrepancy in recent operations (like file size or number of files).&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;The error likely stems from a difference between the current state of the table in Snowflake and what Databricks expects. Reviewing the history should help confirm if there was a shift or an operation that triggered this conflict.&lt;BR /&gt;&lt;BR /&gt;Hope this helps, &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Isi&lt;/P&gt;</description>
    <pubDate>Wed, 30 Jul 2025 11:39:21 GMT</pubDate>
    <dc:creator>Isi</dc:creator>
    <dc:date>2025-07-30T11:39:21Z</dc:date>
    <item>
      <title>Read Snowflake Iceberg tables from Databricks UC</title>
      <link>https://community.databricks.com/t5/data-engineering/read-snowflake-iceberg-tables-from-databricks-uc/m-p/126230#M47658</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hi folks!&lt;/STRONG&gt;&lt;BR /&gt;I'm trying to read Iceberg tables that I created in Snowflake from Databricks using catalog federation. I set up a connection to Snowflake, configured an external location pointing to the S3 folder that contains the Iceberg files, and used that to create a catalog.&lt;/P&gt;&lt;P&gt;The first time, I'm able to query the Iceberg table from Databricks successfully. However, if I update the table in Snowflake and then try to query it again from Databricks, I get the following error:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;EM&gt;Failed to convert the table version 2 to the universal format iceberg. Clone validation failed - Size and number of data files in target table should match with source table. srcTableSize: 168818176, targetTableSize: 314383872 srcTableNumFiles: 25, targetTableNumFiles: 25 SQLSTATE: KD00E&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;The table contains around 5 million rows.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jul 2025 15:34:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/read-snowflake-iceberg-tables-from-databricks-uc/m-p/126230#M47658</guid>
      <dc:creator>jeanptello</dc:creator>
      <dc:date>2025-07-23T15:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Read Snowflake Iceberg tables from Databricks UC</title>
      <link>https://community.databricks.com/t5/data-engineering/read-snowflake-iceberg-tables-from-databricks-uc/m-p/126932#M47805</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/143355"&gt;@jeanptello&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P class=""&gt;It’s possible that there’s a mismatch between what Snowflake has written and what Databricks is trying to read. This often happens if Snowflake has performed an operation that rewrites the table files (like compaction or a bulk update), and then Databricks tries to validate an older version that no longer matches the current state.&lt;/P&gt;&lt;P class=""&gt;I’d recommend:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Refreshing the table from Databricks&lt;/STRONG&gt;&lt;/SPAN&gt; to ensure it’s accessing the most recent version.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;&lt;SPAN class=""&gt;&lt;STRONG&gt;Checking the table history in both Snowflake and Databricks&lt;/STRONG&gt;&lt;/SPAN&gt; to verify whether both systems are seeing the same snapshot, or if there’s a discrepancy in recent operations (like file size or number of files).&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;The error likely stems from a difference between the current state of the table in Snowflake and what Databricks expects. Reviewing the history should help confirm if there was a shift or an operation that triggered this conflict.&lt;BR /&gt;&lt;BR /&gt;Hope this helps, &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Isi&lt;/P&gt;</description>
      <pubDate>Wed, 30 Jul 2025 11:39:21 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/read-snowflake-iceberg-tables-from-databricks-uc/m-p/126932#M47805</guid>
      <dc:creator>Isi</dc:creator>
      <dc:date>2025-07-30T11:39:21Z</dc:date>
    </item>
  </channel>
</rss>

