- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2024 08:17 AM
Hello,
I have deployed successfully a Databricks Job that contains one task of type DLT using Databricks Asset Bundle.
First deployment works well. For this particular Databricks job, I have clicked on "disconnect from source" to do some customization.
Later I did a second deployment using DAB. My second deployment fails stating the following:
Error: cannot create pipeline: The pipeline name 'demo_pipeline' is already used by another pipeline. This check can be skipped by setting `allow_duplicate_names = true` in the request.
- Labels:
-
Workflows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2025 10:47 AM
To fix this, you need to set the allow_duplicate_names parameter to true in your deployment configuration. This parameter allows the deployment to proceed even if the pipeline name conflicts with an existing pipeline.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 03:25 AM
@Walter_C, should this property be set at the same level as name, catalog, channel? I'm getting an error at the schema validation (using the template from databricks bundle schema with databricls-cli v0.260.0), and the deployment does not succeed, due to the duplicated name error.
The intention was to replace the previous DLT with the new one, even though they're similar, only the run_as was changed.