Declarative Pipeline Re-Deployment and existing managed tables exception
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2025 09:04 AM
Hi,
I am facing a issue regarding re deployment of declarative pipeline using asset bundle. On first deployment, I am able to run the pipeline successfully. On execution, pipeline, as expected create tables. However, when I try to re-deploy the pipeline, with bug fixes or new transformations, on execution, it throws existing managed table already exist exception. I assume the re deployments should accept the existing tables created earlier and should continue run successfully with additions.
- Labels:
-
Delta Lake
-
Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2025 09:34 AM
Redeploys with Asset Bundles can safely reuse existing DLT-managed tables.
If you see “managed table already exists”, it usually means:
You’re using plain CREATE TABLE and you should have OR REFRESH part of it
The bundle created a new pipeline pointing at a schema where tables already exist, or
You changed the nature of an existing table (table ↔ view, streaming ↔ batch) without dropping/renaming it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2025 10:01 AM
Managed tables are “owned” by a DLT pipeline. Re-deploying a pipeline that references the same managed tables will fail unless you either:
Drop the existing tables first
Use external tables that are not owned by DLT
Use a separate development schema/pipeline for testing changes
This is by design to protect data integrity and pipeline ownership.
