Technology

Apache XTable

A zero-copy metadata translator (Apache incubating, formerly OneTable) that converts between Iceberg, Delta Lake, and Hudi metadata without copying data files.

7 connections 3 resources

Summary

What it is

A zero-copy metadata translator (Apache incubating, formerly OneTable) that converts between Iceberg, Delta Lake, and Hudi metadata without copying data files.

Where it fits

XTable sits between table formats and query engines, enabling a "write once, read from any format" pattern. Ingest data in Hudi (optimized for CDC) and serve it to Trino and Snowflake via Iceberg metadata — all without data duplication.

Misconceptions / Traps
  • Zero-copy means no data file duplication, but metadata translation still has a cost. Large tables with millions of files can have non-trivial translation overhead.
  • Still in Apache incubation. Documentation and build tooling are rough. Production use requires careful testing.
Key Connections
  • enables Apache Iceberg, Delta Lake, Apache Hudi — cross-format metadata translation
  • solves Vendor Lock-In — prevents table format lock-in
  • competes_with Delta UniForm — different approaches to interoperability

Definition

What it is

A metadata translation layer (Apache incubating, formerly OneTable) that performs zero-copy conversion between Apache Iceberg, Delta Lake, and Apache Hudi metadata. No data files are copied or modified — only metadata is translated.

Why it exists

Organizations ingest data in one table format (e.g., Hudi for low-latency CDC) but need to serve it to engines that prefer another format (e.g., Iceberg for Trino/Snowflake). XTable eliminates the need to maintain multiple copies of the same data in different formats.

Primary use cases

Cross-format interoperability without data duplication, enabling multi-engine access to a single dataset, format migration pathways.

Connections 7

Outbound 6
Inbound 1

Resources 3