Guide, read 10 Nov 2026
Choosing a table format: the checks and the published facts
All guidesOpen the Compute Bill
Check 1: which engines must write the table
List the engines that write, not only the ones that read. Iceberg's home page names Spark, Trino, Flink, Presto, Hive and Impala as engines that can work on the same tables. Delta Lake's home page names Spark, PrestoDB, Flink, Trino, Hive, Snowflake, Google BigQuery, Athena, Redshift, Databricks and Fabric, with Scala, Java, Rust and Python APIs.
Platform support differs by format. Starburst Galaxy creates and writes Iceberg tables but states that it cannot create or write Hudi tables. Dremio Cloud's data-formats page lists Iceberg and Delta Lake and does not list Hudi. Snowflake's Iceberg page did not list Hudi. Fabric's OneLake exposes Iceberg tables as Delta and Delta tables as Iceberg through metadata virtualization.
Check 2: who runs maintenance
Every format needs file compaction and cleanup, and who does it differs by platform. Open-source Iceberg leaves compaction to a job you schedule, with expiring snapshots listed as recommended and rewriting data files as optional. Hudi merge-on-read tables need compaction to fold log files into base files, and Hudi runs cleaning inline after each write by default, keeping the last 10 commits. Delta needs OPTIMIZE and VACUUM, and VACUUM is not triggered automatically.
Managed options exist for each. Databricks predictive optimization covers Delta and Iceberg tables under Unity Catalog. S3 Tables and the Glue Data Catalog cover Iceberg only. Onehouse offers managed table services for Hudi, Iceberg and Delta. See compaction on each platform.
Check 3: what your AWS runtime bundles
The version in your runtime is the version you get. Amazon EMR 7.14.0 packages Iceberg 1.10.1-amzn-1, Delta 3.3.2-amzn-3 and Hudi 1.0.2-amzn-3 with Spark 3.5.8-amzn-0. Project releases read on 2026-11-10 were Iceberg 1.12.0 (September 29, 2026 on the project releases page), Delta Lake 4.4.1 (October 5, 2026) and Hudi 1.2.1 (September 24, 2026).
Delta's compatibility table pairs Delta 4.x releases with Spark 4.0 and 4.1 and the 3.x line with Spark 3.5. A Spark 3.5 runtime therefore constrains which Delta line you can run. The same version check applies to Hudi and Iceberg bundles.
Check 4: whether you need to read across formats
Delta UniForm generates Iceberg and Hudi metadata for Delta tables, and Databricks documents it from Runtime 14.3 LTS. Apache XTable translates metadata between Hudi, Delta and Iceberg and is incubating at the Apache Software Foundation. Both leave the Parquet data files in place.
Cross-reading has costs: Snowflake states that for Iceberg tables managed by an external catalog it does no maintenance, so metadata refresh has to be lined up with whichever engine maintains the table. Read the Delta Lake vs Iceberg page for the feature rows.
Check 5: what leaving would involve
Open formats keep data in files you own, but exit cost sits in the catalog, the maintenance jobs and any proprietary features layered on the format. Databricks predictive optimization works only on Unity Catalog managed tables. Snowflake storage-managed Iceberg tables can be moved to your own storage with CTAS at standard rates. Walk through the specifics in leaving a managed platform.
The maintenance load per format
| Format | Compaction | Cleanup | Layout |
|---|---|---|---|
| Apache Hudi | Compaction folds log files into base files; runs asynchronously by default | Cleaner keeps the last 10 commits by default; timeline archival keeps up to 30 commits in the active timeline | Clustering rewrites files and records a replace commit |
| Apache Iceberg | rewrite_data_files, binpack by default | expire_snapshots (5 days by default); remove_orphan_files (3 days by default) | Sort strategy with sort_order, z-order or hilbert |
| Delta Lake | OPTIMIZE; auto compaction targets 128 MB | VACUUM, 7 days by default | OPTIMIZE ... ZORDER BY |
Check 6: row-level change patterns
If the table takes frequent updates or deletes, check the delete mechanism. Iceberg spec version 3 adds binary deletion vectors; Delta documents deletion vectors as opt-in; Hudi offers copy-on-write and merge-on-read table types, with merge-on-read the one that needs compaction. Hudi's default compaction strategy picks the file groups with the most accumulated unmerged log data, and its trigger can be a count of delta commits, elapsed seconds, or both.
Starburst's Iceberg optimize merges files under a 100 MB threshold by default. Iceberg's own rewrite starts a group at 5 input files. Thresholds like these decide how often compaction runs, so write them down per format before you compare cost.
Sources
- Apache Iceberg home page, read 10 Nov 2026
- Delta Lake home page, read 10 Nov 2026
- Apache Hudi table types, read 10 Nov 2026
- Apache Hudi compaction, read 10 Nov 2026
- Apache Hudi cleaning, read 10 Nov 2026
- Amazon EMR 7.x release versions, read 10 Nov 2026
- Apache Iceberg latest release (GitHub API), read 10 Nov 2026
- Delta Lake latest release (GitHub API), read 10 Nov 2026
- Apache Hudi latest release (GitHub API), read 10 Nov 2026
- Delta Lake releases and Spark compatibility, read 10 Nov 2026
- Starburst Galaxy Hudi, read 10 Nov 2026
- Starburst Galaxy Iceberg, read 10 Nov 2026
- Dremio Cloud data formats, read 10 Nov 2026
- Snowflake Iceberg tables, read 10 Nov 2026
- Snowflake Iceberg table management, read 10 Nov 2026
- Snowflake Iceberg storage, read 10 Nov 2026
- Databricks predictive optimization, read 10 Nov 2026
- Databricks UniForm, read 10 Nov 2026
- Apache XTable, read 10 Nov 2026
- Apache Iceberg table specification, read 10 Nov 2026
- Delta Lake deletion vectors, read 10 Nov 2026
- Fabric OneLake Iceberg tables, read 10 Nov 2026
- Onehouse about, read 10 Nov 2026
- Apache Hudi timeline and archival, read 10 Nov 2026
- Apache Hudi clustering, read 10 Nov 2026
- Apache Iceberg Spark procedures, read 10 Nov 2026
- Delta Lake utility commands (VACUUM), read 10 Nov 2026
- Delta Lake file management, read 10 Nov 2026
Last reviewed 10 Nov 2026.