--- title: The next evolution of Delta - Catalog-Managed Tables description: Delta Lake 4.1.0 introduces catalog-managed tables, shifting the source of truth for table access, metadata, and commits from the filesystem to the catalog.... canonical: https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The next evolution of Delta - Catalog-Managed Tables | daily.dev og:description: Delta Lake 4.1.0 introduces catalog-managed tables, shifting the source of truth for table access, metadata, and commits from the filesystem to the catalog.... og:url: https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn og:image: https://api.daily.dev/og/posts/2gmywKDWn.png og:image:alt: The next evolution of Delta - Catalog-Managed Tables og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # The next evolution of Delta - Catalog-Managed Tables **[Delta Lake Blog](https://daily.dev/sources/delta-lake)** · 9 min read · 0 upvotes · 0 comments ## Summary Delta Lake 4.1.0 introduces catalog-managed tables, shifting the source of truth for table access, metadata, and commits from the filesystem to the catalog. Unity Catalog 0.4.0 is the first open lakehouse catalog to support this model, resolving tables by name instead of storage path, enabling fine-grained governance, enforceable schema constraints, and faster reads/writes by skipping filesystem round trips. The design aligns Delta with Iceberg's catalog-managed approach. A getting-started walkthrough covers enabling the feature in Unity Catalog, creating a catalog-managed table with Spark, and inspecting catalog commit metadata via the Unity Catalog API. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are catalog-managed tables in Delta Lake 4.1.0? Catalog-managed tables are Delta tables where the catalog, rather than the filesystem, brokers access and stores the latest metadata and commits. Clients reference the table by name instead of path, and the catalog resolves storage location, manages concurrency for writes, and provides atomic commits, replacing filesystem PUT-if-absent APIs used previously. _Teams weighing a move to catalog-managed lakehouse tables can track Delta and Unity Catalog updates on daily.dev._ ### Which version of Unity Catalog is needed to support Delta catalog-managed tables? Unity Catalog 0.4.0 is the first open lakehouse catalog to support catalog-managed tables, working alongside Delta Lake 4.1.0. To use it, a table must be created with the delta.feature.catalogManaged property set to supported, otherwise Delta falls back to standard filesystem-based coordination. _Developers setting up catalog-managed workflows can follow related lakehouse tooling news on daily.dev._ ### How does catalog-managed Delta improve write performance compared to filesystem-managed tables? It removes the need for filesystem PUT-if-absent calls by letting clients propose commits directly to the catalog, with an option for inline commits that skip the 100ms+ filesystem write entirely. Staged commits still use optimistic concurrency control, and ratified commits are periodically published to the filesystem's _delta_log for long-term storage. _Engineers optimizing lakehouse write latency can keep up with Delta protocol changes via daily.dev._ ## Similar posts on daily.dev - [How Unity Catalog managed tables bring interoperability, performance, and unified governance to the Lakehouse](https://daily.dev/posts/how-unity-catalog-managed-tables-bring-interoperability-performance-and-unified-governance-to-the--8wtwlazxm) · databricks · 0 upvotes · 0 comments - [Introducing the UC Delta API](https://daily.dev/posts/introducing-the-uc-delta-api-phw3nzgrc) · Delta Lake Blog · 0 upvotes · 0 comments - [The Convergence of Open Table Formats and Open Catalogs: Catalog Commits is Generally Available](https://daily.dev/posts/the-convergence-of-open-table-formats-and-open-catalogs-catalog-commits-is-generally-available-smdzq51ud) · databricks · 0 upvotes · 0 comments - [Enterprise Tableflow: Delta Lake, Unity Catalog, and Azure](https://daily.dev/posts/enterprise-tableflow-delta-lake-unity-catalog-and-azure-kjwsdbkkv) · Confluent Blog · 0 upvotes · 0 comments - [Delta Grows Up: Writes, Unity Catalog and Time Travel](https://daily.dev/posts/delta-grows-up-writes-unity-catalog-and-time-travel-j5aia1x3q) · DuckDB · 0 upvotes · 0 comments --- Tags: [#big-data](https://daily.dev/tags/big-data), [#data-engineering](https://daily.dev/tags/data-engineering), [#apache-iceberg](https://daily.dev/tags/apache-iceberg), [#unity-catalog](https://daily.dev/tags/unity-catalog) [View this post on daily.dev](https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"The next evolution of Delta - Catalog-Managed Tables","url":"https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn"},"datePublished":"2026-08-16T08:53:33.689Z","dateModified":"2026-08-16T08:55:59.295Z","description":"Delta Lake 4.1.0 introduces catalog-managed tables, shifting the source of truth for table access, metadata, and commits from the filesystem to the catalog....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1b3b199ef53adb3d95343c8a60e28d97?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/1b3b199ef53adb3d95343c8a60e28d97?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Delta Lake Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Delta Lake Blog","logo":"https://media.daily.dev/image/upload/s--7f2q9Asf--/f_auto,q_auto/v1786870393/logos/delta-lake?_a=BAMAMicg0","url":"https://daily.dev/sources/delta-lake"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"big-data,data-engineering,apache-iceberg,unity-catalog","timeRequired":"PT9M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Delta Lake Blog","item":"https://daily.dev/sources/delta-lake"},{"@type":"ListItem","position":3,"name":"The next evolution of Delta - Catalog-Managed Tables"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-next-evolution-of-delta---catalog-managed-tables-2gmywkdwn#faq","mainEntity":[{"@type":"Question","name":"What are catalog-managed tables in Delta Lake 4.1.0?","acceptedAnswer":{"@type":"Answer","text":"Catalog-managed tables are Delta tables where the catalog, rather than the filesystem, brokers access and stores the latest metadata and commits. Clients reference the table by name instead of path, and the catalog resolves storage location, manages concurrency for writes, and provides atomic commits, replacing filesystem PUT-if-absent APIs used previously. Teams weighing a move to catalog-managed lakehouse tables can track Delta and Unity Catalog updates on daily.dev."}},{"@type":"Question","name":"Which version of Unity Catalog is needed to support Delta catalog-managed tables?","acceptedAnswer":{"@type":"Answer","text":"Unity Catalog 0.4.0 is the first open lakehouse catalog to support catalog-managed tables, working alongside Delta Lake 4.1.0. To use it, a table must be created with the delta.feature.catalogManaged property set to supported, otherwise Delta falls back to standard filesystem-based coordination. Developers setting up catalog-managed workflows can follow related lakehouse tooling news on daily.dev."}},{"@type":"Question","name":"How does catalog-managed Delta improve write performance compared to filesystem-managed tables?","acceptedAnswer":{"@type":"Answer","text":"It removes the need for filesystem PUT-if-absent calls by letting clients propose commits directly to the catalog, with an option for inline commits that skip the 100ms+ filesystem write entirely. Staged commits still use optimistic concurrency control, and ratified commits are periodically published to the filesystem's _delta_log for long-term storage. Engineers optimizing lakehouse write latency can keep up with Delta protocol changes via daily.dev."}}]} ```