<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data-Lakehouse on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/data-lakehouse/</link>
    <description>Recent content in Data-Lakehouse on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/data-lakehouse/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apache Polaris vs Lakekeeper vs Gravitino in 2026: Which Iceberg Catalog Should You Actually Run?</title>
      <link>https://www.pistack.xyz/posts/2026-10-21-iceberg-rest-catalogs-polaris-lakekeeper-gravitino-guide/</link>
      <pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-21-iceberg-rest-catalogs-polaris-lakekeeper-gravitino-guide/</guid>
      <description>&lt;p&gt;Your Iceberg tables are not the hard part anymore. Every engine speaks the format, and object storage is cheap. What breaks at 3am is the &lt;strong&gt;catalog&lt;/strong&gt;: the thing that answers &amp;ldquo;where does this table live, who may read it, and which storage credential do I hand out?&amp;rdquo; Get that wrong and you end up with three engines writing to the same bucket under three different metadata pointers, and a data lake that quietly forks itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
