<?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: Can we have a depend-on for jobs to run on two different dabs? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/can-we-have-a-depend-on-for-jobs-to-run-on-two-different-dabs/m-p/116264#M45282</link>
    <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/160888"&gt;@vivi007&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, you can create dependencies between jobs in different DABs (Databricks Asset Bundles), but this requires a different approach than task dependencies within a single DAB.&lt;/P&gt;&lt;P&gt;Since DABs are designed to be independently deployable units, direct dependencies between them aren't built into the DAB structure itself. However, you can implement cross-DAB job dependencies using a few methods:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Databricks Workflows API&lt;/STRONG&gt;: You can create a programmatic solution using the Workflows API to check the completion status of a job in one DAB before triggering a job in another DAB.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;External orchestration tools&lt;/STRONG&gt;: Tools like Apache Airflow can orchestrate workflows across multiple DABs by monitoring job completion and triggering dependent jobs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Event-based triggers&lt;/STRONG&gt;: Set up the first DAB's job to publish an event (e.g., to a webhook or message queue) upon completion, and configure the second DAB's job to start when it receives this event.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Delta Live Tables (DLT) Pipeline Dependencies&lt;/STRONG&gt;: If you're using DLT pipelines, you can create dependencies between pipelines that exist in different DABs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Scheduled dependencies&lt;/STRONG&gt;: Configure the dependent job with a schedule that starts after the expected completion time of the prerequisite job, possibly with additional checks.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Remember that when implementing cross-DAB dependencies, you'll need to handle error scenarios and retries appropriately, as well as ensure proper access controls are in place between the different asset bundles.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Apr 2025 04:14:17 GMT</pubDate>
    <dc:creator>lingareddy_Alva</dc:creator>
    <dc:date>2025-04-23T04:14:17Z</dc:date>
    <item>
      <title>Can we have a depend-on for jobs to run on two different dabs?</title>
      <link>https://community.databricks.com/t5/data-engineering/can-we-have-a-depend-on-for-jobs-to-run-on-two-different-dabs/m-p/116230#M45274</link>
      <description>&lt;P&gt;If there are two different DABs. Can we have a dependency for one job from one DAB to run after a job run from another DAB?&amp;nbsp; Similar to how tasks can depend on each other to run one after the other in the same DAB. Can we have the same for two different DABs?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Apr 2025 17:59:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/can-we-have-a-depend-on-for-jobs-to-run-on-two-different-dabs/m-p/116230#M45274</guid>
      <dc:creator>vivi007</dc:creator>
      <dc:date>2025-04-22T17:59:01Z</dc:date>
    </item>
    <item>
      <title>Re: Can we have a depend-on for jobs to run on two different dabs?</title>
      <link>https://community.databricks.com/t5/data-engineering/can-we-have-a-depend-on-for-jobs-to-run-on-two-different-dabs/m-p/116264#M45282</link>
      <description>&lt;P&gt;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/160888"&gt;@vivi007&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes, you can create dependencies between jobs in different DABs (Databricks Asset Bundles), but this requires a different approach than task dependencies within a single DAB.&lt;/P&gt;&lt;P&gt;Since DABs are designed to be independently deployable units, direct dependencies between them aren't built into the DAB structure itself. However, you can implement cross-DAB job dependencies using a few methods:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Databricks Workflows API&lt;/STRONG&gt;: You can create a programmatic solution using the Workflows API to check the completion status of a job in one DAB before triggering a job in another DAB.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;External orchestration tools&lt;/STRONG&gt;: Tools like Apache Airflow can orchestrate workflows across multiple DABs by monitoring job completion and triggering dependent jobs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Event-based triggers&lt;/STRONG&gt;: Set up the first DAB's job to publish an event (e.g., to a webhook or message queue) upon completion, and configure the second DAB's job to start when it receives this event.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Delta Live Tables (DLT) Pipeline Dependencies&lt;/STRONG&gt;: If you're using DLT pipelines, you can create dependencies between pipelines that exist in different DABs.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Scheduled dependencies&lt;/STRONG&gt;: Configure the dependent job with a schedule that starts after the expected completion time of the prerequisite job, possibly with additional checks.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Remember that when implementing cross-DAB dependencies, you'll need to handle error scenarios and retries appropriately, as well as ensure proper access controls are in place between the different asset bundles.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Apr 2025 04:14:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/can-we-have-a-depend-on-for-jobs-to-run-on-two-different-dabs/m-p/116264#M45282</guid>
      <dc:creator>lingareddy_Alva</dc:creator>
      <dc:date>2025-04-23T04:14:17Z</dc:date>
    </item>
  </channel>
</rss>

