Is Delta Lake dead?

Summary

• Delta Lake's release record shows an active project: Delta Lake 4.4.0 shipped on August 20, 2026 with Apache Spark 4.2 support, and the 4.4.1 patch followed on October 5, 2026.
• Delta Lake is a Linux Foundation sub-project under the Apache 2.0 license, and it describes itself as "not controlled by any single company."
• Its 2026 releases added a Kernel-based Flink connector, Unity Catalog Delta REST API integration, identity columns in SQL DDL, and atomic, incremental Iceberg conversion in UniForm.
• Delta Lake and Apache Iceberg interoperate. UniForm lets Iceberg and Hudi clients read Delta tables, Iceberg documents an action that converts supported Delta tables, and Unity Catalog manages both formats.

Is Delta Lake dead?

The project's release record answers this. Delta Lake 4.4.0, published on August 20, 2026, added Apache Spark 4.2 support, identity columns in SQL DDL, and Unity Catalog Delta API integration for Delta Kernel and the experimental Flink connector. A 4.4.1 patch followed on October 5, 2026. Delta Lake is a Linux Foundation sub-project that calls itself "an independent open-source project and not controlled by any single company," and Unity Catalog uses Delta Lake as the default format for managed tables while also supporting Apache Iceberg. The more useful question is whether Delta Lake fits the engines that must read and write your tables.

Recent Delta Lake releases

Release	Published	Notable changes (from the release notes)
4.4.1	2026-10-05	Patch: safer maintenance for catalog-managed tables; snapshot fix for coordinated commits
4.4.0	2026-08-20	Apache Spark 4.2 support; identity columns in SQL DDL; UC Delta API for Delta Kernel and the experimental Flink connector
4.3.0	2026-06-18	Spark integration with the Unity Catalog Delta REST API; replaceOn and replaceUsing DataFrame APIs; atomic, incremental Iceberg conversion in UniForm
4.2.0	2026-04-16	New Kernel-based Flink connector (experimental); Delta Kernel support for geospatial types, generally available Variant columns and collations
4.1.0	2026-02-26	Apache Spark 4.1.0 support; Spark V2 connector based on Delta Kernel; server-side planning (preview) following the Iceberg REST Catalog API
4.0.0	2025-06-09	Delta Connect for Spark Connect; Variant data type; DROP FEATURE without truncating history

The older 3.3 line still receives fixes: Delta Lake 3.3.3 shipped on August 12, 2026.

Delta Lake vs Apache Iceberg: how they compare

Capability	Delta Lake	Apache Iceberg
Governance and license	Linux Foundation sub-project; Apache 2.0	Apache Software Foundation; Apache 2.0
Specification	Transaction log protocol (PROTOCOL.md), with all table metadata stored alongside the data	Table spec covering "immutable file formats: Parquet, Avro, and ORC"
Documented features	ACID transactions, schema enforcement, time travel, upserts and deletes, streaming and batch unification	Expressive SQL, full schema evolution, hidden partitioning, time travel and rollback, data compaction
Catalog API	Unity Catalog Delta REST API, used by Delta Spark since 4.3.0	Iceberg REST Catalog API, published as an OpenAPI spec
Non-JVM implementations	Delta Kernel's Rust libraries; delta-rs, "a native Rust library for Delta Lake, with bindings into Python"	PyIceberg; iceberg-rust
Cross-format path	UniForm lets Iceberg and Hudi clients read Delta tables (read-only from their side)	snapshotDeltaLakeTable in the iceberg-delta-lake module converts a Delta table into a new Iceberg table (documented for minReaderVersion 1 and minWriterVersion 2)

How to choose a format by workload

• Engines that must write. List every engine that writes, then confirm a documented writer for each format. Read access alone can come from a translation layer such as UniForm.
• The catalog you run. A catalog that speaks the Iceberg REST API serves Iceberg tables directly. Unity Catalog serves Delta clients through the Unity REST API and Iceberg clients through its Iceberg REST catalog.
• Table features you depend on. Check that your engines support the specific features you use, such as Variant columns or deletion vectors, for the format and version you pick.

How Databricks approaches Delta Lake and Apache Iceberg

Databricks' public position is support for both formats in Unity Catalog, with interoperability between them. Unity Catalog managed tables are "the default and recommended table type in Databricks for Delta Lake and Apache Iceberg," and Databricks creates a Delta Lake table unless you specify USING iceberg. The Iceberg REST catalog gives Iceberg clients read, write and create access to managed Iceberg tables, and read-only access to Delta tables with Iceberg reads (UniForm) enabled. Available in Databricks Runtime 14.3 LTS and above, Iceberg reads "configure Delta Lake tables to automatically generate Iceberg metadata." For an existing table, the docs use:

ALTER TABLE table_name SET TBLPROPERTIES(
  'delta.columnMapping.mode' = 'name',
  'delta.enableIcebergCompatV2' = 'true',
  'delta.universalFormat.enabledFormats' = 'iceberg'
)

FAQs

What is Databricks' position on Delta Lake and Apache Iceberg?

Databricks' documentation makes Delta Lake the default format for Unity Catalog managed tables and lists managed tables as the recommended type for both Delta Lake and Apache Iceberg. Delta Lake 4.3.0 and 4.4.0 also added integration with the Unity Catalog Delta REST API.

Should I choose Delta Lake or Apache Iceberg?

Choose by the engines that must write to your tables and the catalog you'll run. Both formats are open, Apache 2.0 licensed and governed by a foundation, and both have implementations outside the JVM.

Can Delta Lake and Iceberg tables work together?

Yes. UniForm lets Iceberg and Hudi clients read Delta tables, Iceberg's snapshotDeltaLakeTable action converts a supported Delta table into a new Iceberg table, and Unity Catalog governs both formats side by side.