Draft:Open Table Format
Review waiting, please be patient.
This may take 4 months or more, since drafts are reviewed in no specific order. There are 4,550 pending submissions waiting for review.
Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Reviewer tools
|
An open table format is an open specification for a
metadata layer that organizes a collection of data files in
object storage into a single logical table, adding
database-like guarantees such as ACID transactions, schema evolution,
and point-in-time ("time travel") queries. Open table formats sit above open
file formats such as Apache Parquet and below the query engines and
data catalogs that read and write the data, and they are a foundational
storage layer of the lakehouse architecture.[1]
The most widely used open table formats are Delta Lake (Software), Apache Iceberg, and Apache Hudi, together with the more recent Apache Paimon. They emerged between roughly 2016 and 2020 to bring the reliability and management features of a data warehouse to the low-cost, open storage of a data lake.[1][2]
Concept and motivation
[edit]A data lake stores data as files in object storage, typically in open columnar formats such as Apache Parquet or ORC. A file format defines how the bytes of an individual file are laid out, but it does not define which files make up a table, nor does it coordinate concurrent readers and writers. Early conventions such as Apache Hive tables tracked table membership through directory layout, which made operations like updating rows, changing a table's schema, or reading a table while it was being written unreliable.[2]
An open table format addresses this by maintaining a separate metadata layer that records the exact set of files belonging to each version of a table. This lets engines commit changes atomically and read a consistent view of the table while it is being written. It also lets a table's schema and partitioning change over time without rewriting existing data. Because the specification and the data are both open, multiple independent engines can read and write the same table.[1][2]
How they work
[edit]Although the formats differ in detail, they share a common model: a metadata layer tracks which data files constitute each committed version, or snapshot, of a table. Reading a table means resolving the current snapshot to a list of files; writing means producing new data files and then atomically committing new metadata that points to them. Retaining older snapshots enables time-travel queries and rollback, and comparing snapshots supports incremental processing.[2][1]
Major formats
[edit]Delta Lake was developed at Databricks and released as open source in 2019; it was later contributed to the Linux Foundation. It stores table metadata in a transaction log kept alongside the Parquet data files.[3]
Apache Iceberg was started at Netflix by Ryan Blue and Dan Weeks in 2017 and became a top-level Apache Software Foundation project in 2020. It is known for hidden partitioning and schema and partition evolution that do not require rewriting existing data.[4][5]
Apache Hudi (from "Hadoop Upserts Deletes and Incrementals") originated at Uber around 2016 to support efficient row-level upserts and incremental data ingestion, and later became an Apache Software Foundation project.[6]
Apache Paimon began as Flink Table Store within the Apache Flink project and entered the Apache incubator in 2023, where it was renamed; it is designed as a streaming-first lake format.[7]
Interoperability
[edit]Because several formats coexist, interoperability between them has become an active area of development. By the mid-2020s, reporting on Delta Lake and Iceberg described the two formats as converging rather than competing.[8] One marker of that convergence was Databricks' 2024 acquisition of Tabular, a company founded by Iceberg's original creators, after which Databricks said it aimed to move the two formats toward a common standard.[9]
Format-level convergence
[edit]Convergence has occurred at the level of the on-disk format itself, most visibly between Iceberg and Delta Lake. With version 3 of the Iceberg specification, the two formats aligned their data layer: Parquet data files and deletion vectors (side files that mark deleted rows without rewriting data) became interchangeable between them without conversion. Their metadata layers, however, remained separate.[10]
More recent proposals, still unratified as of 2026, would align the metadata layer too. Apache Iceberg's proposed version 4 adds an "adaptive metadata tree" that restructures table metadata to make frequent, small commits cheaper.[11] A corresponding proposal in the Delta Lake project would adopt the Iceberg v4 metadata tree as Delta's native metadata format, which its authors describe as work done "collaborating with the Iceberg community." Both remain proposals under community review rather than shipped features.[10]
Translation tools
[edit]Where the formats have not converged, translation tools bridge them. Databricks' UniForm, introduced with Delta Lake 3.0 in 2023, lets a Delta table also expose Iceberg- and Hudi-compatible metadata over a single copy of the data, and Apache XTable (formerly OneTable) translates table metadata among the three formats without rewriting the underlying data files.[12]
See also
[edit]References
[edit]- ^ a b c d "Data Lakehouse: A survey and experimental study". Information Systems. 127. 2024. doi:10.1016/j.is.2024.102460.
- ^ a b c d Analyzing and Comparing Lakehouse Storage Systems (PDF). Conference on Innovative Data Systems Research (CIDR). 2023.
- ^ Lardinois, Frederic (2019-10-15). "Databricks brings its Delta Lake open source project to the Linux Foundation". TechCrunch.
- ^ "Apache Iceberg". Apache Software Foundation.
- ^ "Apache Iceberg — Project Incubation Status". Apache Software Foundation.
- ^ "Apache Hudi at Uber: Engineering for Trillion-Record-Scale Data Lake Operations". Uber Engineering Blog.
- ^ "What is Paimon (incubating) (formerly Flink Table Store)?". Apache Software Foundation.
- ^ Clark, Lindsay (2025-04-15). "Delta Lake and Iceberg communities collide – in a good way". The Register.
- ^ "Databricks is buying data optimization startup Tabular". CNBC. 2024-06-04.
- ^ a b "[PROTOCOL RFC] Adopt the Iceberg v4 manifest tree as Delta's native content metadata format". delta-io/delta issue #6640. Linux Foundation.
- ^ "v4: add manifest write support". apache/iceberg issue #16694. Apache Software Foundation.
- ^ "Databricks' Delta Lake 3.0 bridges compatibility gaps with Apache Iceberg and Hudi". SiliconANGLE. 2023-06-28.
Category:Data management Category:Cloud storage Category:Open formats
