<?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 Databricks + Apache Iceberg = advantageous or wasted effort due to duplicate functionality ? in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/databricks-apache-iceberg-advantageous-or-wasted-effort-due-to/m-p/81366#M1445</link>
    <description>&lt;P&gt;Trying to design a Lakehouse. Spark is at the base layer. Now wondering if adding Apache Iceberg sitting below Spark will be of help, or, not ? Preferring Iceberg for its auto indexing, ACID query facilities over big hetergenous datasets. Wonder if its a wise choice??&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2024 18:40:35 GMT</pubDate>
    <dc:creator>ag2all</dc:creator>
    <dc:date>2024-07-31T18:40:35Z</dc:date>
    <item>
      <title>Databricks + Apache Iceberg = advantageous or wasted effort due to duplicate functionality ?</title>
      <link>https://community.databricks.com/t5/administration-architecture/databricks-apache-iceberg-advantageous-or-wasted-effort-due-to/m-p/81366#M1445</link>
      <description>&lt;P&gt;Trying to design a Lakehouse. Spark is at the base layer. Now wondering if adding Apache Iceberg sitting below Spark will be of help, or, not ? Preferring Iceberg for its auto indexing, ACID query facilities over big hetergenous datasets. Wonder if its a wise choice??&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2024 18:40:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/databricks-apache-iceberg-advantageous-or-wasted-effort-due-to/m-p/81366#M1445</guid>
      <dc:creator>ag2all</dc:creator>
      <dc:date>2024-07-31T18:40:35Z</dc:date>
    </item>
    <item>
      <title>Re: Databricks + Apache Iceberg = advantageous or wasted effort due to duplicate functionality ?</title>
      <link>https://community.databricks.com/t5/administration-architecture/databricks-apache-iceberg-advantageous-or-wasted-effort-due-to/m-p/82015#M1497</link>
      <description>&lt;P&gt;Hello, if you're planning on building your own open source stack of spark+iceberg, it can be a good choice.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're on Databricks, however, you're going to miss out a *lot* on delta features that are baked into the platform. Specifically compute + storage performance based optimisations and UC integrations. Delta has ACID compliance, works beautifully with large datasets and you have many performance choices with liquid clustering or legacy z ordering.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you're integrating with other systems that are only iceberg compatible, check out uniform to write out additional metadata so other systems can read from it:&amp;nbsp;&lt;A href="https://docs.databricks.com/en/delta/uniform.html" target="_blank"&gt;https://docs.databricks.com/en/delta/uniform.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2024 10:10:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/databricks-apache-iceberg-advantageous-or-wasted-effort-due-to/m-p/82015#M1497</guid>
      <dc:creator>holly</dc:creator>
      <dc:date>2024-08-06T10:10:06Z</dc:date>
    </item>
  </channel>
</rss>

