Apache Iceberg is a high-performance table format for large analytic datasets that provides ACID transactions and schema evolution on object stores and distributed filesystems (data lakehouse / data management).
- Table format for huge analytic datasets on data lakes and object storage (data lakehouse)
- Supports ACID transactions and concurrent writers via snapshot-based operations (data consistency)
- Enables schema and partition evolution without rewriting full tables (data management)
- Integrates with distributed compute engines such as Structured Query Language (SQL) query platforms and processing frameworks (data processing)
- Provides hidden partitioning, time-travel queries, and metadata for scalable planning (data optimization)
More about Apache Iceberg
More About Apache Iceberg
Apache Iceberg is a table format for large analytic datasets that runs on top of distributed filesystems and object stores, designed to make data lakes behave more like traditional analytical databases (data lakehouse). It defines how data files, metadata, and manifests are structured and maintained so that query engines can read and write tables reliably at scale.
The project focuses on reliable table management for petabyte-scale data by introducing a versioned metadata layer and immutable snapshots (data management). Each table update creates a new snapshot that references a specific set of data files, which enables atomic changes and isolation for readers and writers (data consistency). This approach supports ACID-style operations in environments where underlying storage is not transactional.
Apache Iceberg supports schema evolution and partition evolution without requiring full table rewrites (data management). Columns can be added, renamed, or dropped, and partitions can change over time while preserving query compatibility. Hidden partitioning allows query planners to leverage partition information without exposing partition columns directly to users, reducing the risk of incorrect query filters and improving plan efficiency (data optimization).
The format defines clear specifications for table metadata, manifests, partition specs, and data file layouts (data format specification). It is designed to be engine-agnostic, so multiple compute engines can operate on the same tables concurrently (data interoperability). Common integrations include SQL query engines and distributed processing frameworks, which read and write Iceberg tables using native connectors or catalog integrations.
Iceberg catalogs manage table locations, schemas, and snapshots, and can be backed by systems such as metastore services, key-value stores, or other catalog backends (metadata management). Catalogs provide a namespace for tables, track current snapshots, and coordinate concurrent operations across different clients.
Additional capabilities include time-travel queries and rollback to earlier snapshots (data governance). Because each snapshot records a complete table state through metadata, readers can query historical versions for auditing, debugging, or reproducibility. The metadata layout also enables query engines to prune data files efficiently based on statistics and partition information, reducing scan overhead on large datasets (query optimization).
In enterprise environments, Apache Iceberg is used to standardize table storage on data lakes, support multi-engine analytics, and enforce reliable change management on shared datasets (enterprise data architecture). It fits into categories such as data lakehouse table formats, big data storage formats, and transactional data lake management, and is used as a foundational layer for analytics, BI, Machine Learning (ML), and Extract, Transform, Load (ETL) workloads.