<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to deploy a DLT Pipeline? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123600#M47034</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/133094"&gt;@jeremy98&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;When a DLT pipeline creates a table, this table can only be written to by the pipeline that created it. If another pipeline tries to write data to this table the pipeline will error.&lt;BR /&gt;&lt;BR /&gt;The solution is quite simple, parametrize your DAB template in such way that each developer during DAB deployment to DEV will have its own dedicated catalog. You can refere to below article when this approach is explained in details:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.advancinganalytics.co.uk/blog/avoid-delta-live-table-conflicts-with-databricks-asset-bundles" target="_blank"&gt;Avoid Delta Live Table Pipeline Conflicts with Parameterised Databricks Asset Bundles&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 02 Jul 2025 07:59:04 GMT</pubDate>
    <dc:creator>szymon_dybczak</dc:creator>
    <dc:date>2025-07-02T07:59:04Z</dc:date>
    <item>
      <title>How to deploy a DLT Pipeline?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123595#M47033</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hi community,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;My team and I have been working on manually creating our first DLT pipeline. However, when we tried importing it into DABs, we encountered an issue in the dev workspace: we are unable to deploy the same DLT pipeline multiple times because the source is already being used by another instance of the same pipeline.&lt;/P&gt;&lt;P&gt;This prevents us from testing properly in the dev environment. Has anyone experienced a similar issue? How can we resolve this?&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 07:19:30 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123595#M47033</guid>
      <dc:creator>jeremy98</dc:creator>
      <dc:date>2025-07-02T07:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: How to deploy a DLT Pipeline?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123600#M47034</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/133094"&gt;@jeremy98&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;When a DLT pipeline creates a table, this table can only be written to by the pipeline that created it. If another pipeline tries to write data to this table the pipeline will error.&lt;BR /&gt;&lt;BR /&gt;The solution is quite simple, parametrize your DAB template in such way that each developer during DAB deployment to DEV will have its own dedicated catalog. You can refere to below article when this approach is explained in details:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.advancinganalytics.co.uk/blog/avoid-delta-live-table-conflicts-with-databricks-asset-bundles" target="_blank"&gt;Avoid Delta Live Table Pipeline Conflicts with Parameterised Databricks Asset Bundles&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 07:59:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123600#M47034</guid>
      <dc:creator>szymon_dybczak</dc:creator>
      <dc:date>2025-07-02T07:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to deploy a DLT Pipeline?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123628#M47044</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Thanks for your response! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;Duplicating the catalog for this does feel a bit unusual. I understand the reasoning behind it, though it’s not the cleanest approach. Still, I suppose it’s acceptable for a DEV workspace.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jul 2025 10:44:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-to-deploy-a-dlt-pipeline/m-p/123628#M47044</guid>
      <dc:creator>jeremy98</dc:creator>
      <dc:date>2025-07-02T10:44:43Z</dc:date>
    </item>
  </channel>
</rss>

