# Unity Catalog OSS 0.7.0 enables native Iceberg tables by default

News, 13 Oct 2026

**The short answer.** Unity Catalog 0.7.0 was published on 2026-10-13. Per its notes, any engine speaking the Iceberg REST protocol can create, write, read, rename and drop Iceberg tables, native Iceberg tables are enabled by default, and dropped managed tables are deleted after a default 7-day delay.

The release notes lead with Iceberg REST catalog APIs for table operations. Their Spark example points Iceberg's own REST catalog at the server's `/api/2.1/unity-catalog/iceberg` path with Iceberg 1.11.0 runtime packages, with no UC connector needed.

Two behavior changes need a look before upgrading. Servers that never set `server.iceberg-table.enabled` now accept Iceberg creates and commits; setting it to false keeps the old behavior. Dropping a managed table, volume or model now reclaims its storage after `server.storage-cleanup.initial-delay`, default 7 days.

Other items: health and metrics endpoints on a dedicated `--obs-port`, multi-instance authorization refresh, and a loadTable signal telling clients which maintenance operations the catalog permits.

## Sources

- Unity Catalog v0.7.0 release notes, GitHub: https://github.com/unitycatalog/unitycatalog/releases/tag/v0.7.0 (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/news/unity-catalog-0-7-0-iceberg-rest/
