Hudi 1.0 is the most powerful release to date for data lakehouses. Read the blog for details:
Secondary Indexing, Expression Indexes, Partial Updates, Non-blocking Concurrency Control, New LSM timeline, +more: hudi.apache.org/blog/2024/12…#datalakehouse#opentableformat
Apache XTable (Incubating) is how a Hudi table becomes an Iceberg table without rewrites.
Same data files on object storage. Two metadata layers describing them — one Hudi, one Iceberg — each consumable by a different engine ecosystem.
The interop pattern that lets the engineering decision be "write to the format with the best primitives for our workload" — not "write to what our downstream engines understand."
Links ↓
#ApacheHudi#ApacheXTable
Storage format is versioned. Hudi 1.x ships backward-compatible writes — upgrade readers first, then writers in any order. No coordinated downtime.
Links ↓
#ApacheHudi#StorageDesign
Tencent Cloud EMR added native Apache Hudi support in v2.2.0 as a first-class BigData component.
Native Hudi on managed Spark + Flink. Data on HDFS, COS, or CHDFS ↓
Open lakehouse is cloud-portable in a way closed proprietary alternatives can't match — tables move across clouds without rewrites.
Links ↓
#ApacheHudi#CloudPortability
Listing partitions on S3 doesn't scale. Hudi's metadata table fixes this.
Cloud object storage LIST calls are slow — seconds on small tables, many minutes on partitioned tables with thousands of folders. Every reader and writer pays.