#iceberg

Every Iceberg table accumulates structural debt from its first commit. Files fragment. Snapshots pile...

Step by step: the Apache Rust Iceberg REST client against seven Iceberg catalogs. It logs in to five of them, and on every one it logs in to, all 13 endpoints it implements answer — 7 reads on three catalogs and 11 writes on the local one, with no failures. The two AWS catalogs need SigV4, which it cannot send, so Rust reaches them through two other crates whose operation sets differ from its own.

The AWS Glue Data Catalog's managed table optimizers are the path of least resistance for Iceberg...

Every query against an Iceberg table is a negotiation about how much data the engine is allowed to...

Step by step: timing the Rust and Python Iceberg REST clients on the same operations, on a local catalog and on BigLake and OneLake. Rust is 2x to 4x faster per call on the same machine, the two are even over the internet, and Python takes half a second longer to start on every catalog.

Governance in an Apache Iceberg lakehouse is not a feature you enable. It is an architecture you...

Every write to an Apache Iceberg table creates a new snapshot. Every snapshot pins references to data...

Amazon S3 Tables solves a real problem. If you have ever spent a weekend debugging a failed...

Why I chose this topic: I spent three weeks debugging a "simple" read query that took four minutes...

Melting of the submerged part of an iceberg, its keel, releases freshwater below the ocean surface,...

Original Japanese article: Icebergは本当にベンダーロックインを解消したのか考えてみた Introduction I'm Aki, an...

Step by step: timing the Rust and Python Iceberg REST clients on the same operations, on a local catalog and on BigLake and OneLake. Rust is 2x to 4x faster per call on the same machine, the two are even over the internet, and Python takes half a second longer to start on every catalog.