Iceberg v4 Performance: Root Manifests and Calls
Apache Iceberg v4 discussion should focus on planning cost, metadata layout, and object storage round trips, not vague claims about faster tables.
The archive
Writing, page 24
657 posts on Apache Iceberg, lakehouse architecture, data engineering and applied AI.
What Is LTAP in the Lakehouse?
Lakehouse transactional analytical processing is useful only when teams define freshness, isolation, and workload boundaries clearly.
The Model Is Not the Moat
Enterprise AI advantage increasingly comes from governed context, semantic models, and operational data contracts, not only from model choice.
PyIceberg at Scale Without Apache Spark
Python-first Iceberg work is useful when it stays honest about what Python should and should not do.
The Real-Time Lakehouse with Streaming and Iceberg
The real-time lakehouse is not one engine. It is a contract between streams, table commits, query paths, and freshness expectations.
REST Catalog V2 LoadTable and Client Capability
REST Catalog V2 LoadTable work matters because clients and catalogs need explicit contracts, not optimistic assumptions.
Rust vs C++ in Native Iceberg Scan Operators
The Rust versus C++ discussion is really about table-layer execution safety, interoperability, and performance envelopes.
Server-Side Commit Deconflicting in REST Catalogs
Server-side commit deconflicting is about moving concurrency control closer to the catalog contract.
Snowflake Interoperable Lakehouse Lessons
Interoperable lakehouse announcements matter when they change production contracts, not just import and export narratives.
Unity AI Gateway vs Apache Polaris Control Planes
The right comparison is not vendor scoreboard. It is closed AI governance gateway versus open catalog control plane.