<?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 Trigger table sync from job in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/trigger-table-sync-from-job/m-p/125984#M47599</link>
    <description>&lt;P&gt;When setting up a table sync using the UI, a pipeline is created, but this is not visible through the Pipelines overview–presumably because it's "managed" by the target table (at least this is where you manage the data ingest process.&lt;/P&gt;&lt;P&gt;This means that if the table sync is running in triggered mode, it's not possible to trigger it using a &lt;A href="https://docs.databricks.com/gcp/en/jobs/pipeline" target="_self"&gt;pipeline task for jobs&lt;/A&gt;, which is otherwise possible (a "pipeline task can be the triggering mechanism for a triggered pipeline"), but we can't look up the pipeline.&lt;/P&gt;&lt;P&gt;What's the recommended approach here?&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jul 2025 11:04:23 GMT</pubDate>
    <dc:creator>Malthe</dc:creator>
    <dc:date>2025-07-22T11:04:23Z</dc:date>
    <item>
      <title>Trigger table sync from job</title>
      <link>https://community.databricks.com/t5/data-engineering/trigger-table-sync-from-job/m-p/125984#M47599</link>
      <description>&lt;P&gt;When setting up a table sync using the UI, a pipeline is created, but this is not visible through the Pipelines overview–presumably because it's "managed" by the target table (at least this is where you manage the data ingest process.&lt;/P&gt;&lt;P&gt;This means that if the table sync is running in triggered mode, it's not possible to trigger it using a &lt;A href="https://docs.databricks.com/gcp/en/jobs/pipeline" target="_self"&gt;pipeline task for jobs&lt;/A&gt;, which is otherwise possible (a "pipeline task can be the triggering mechanism for a triggered pipeline"), but we can't look up the pipeline.&lt;/P&gt;&lt;P&gt;What's the recommended approach here?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jul 2025 11:04:23 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/trigger-table-sync-from-job/m-p/125984#M47599</guid>
      <dc:creator>Malthe</dc:creator>
      <dc:date>2025-07-22T11:04:23Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger table sync from job</title>
      <link>https://community.databricks.com/t5/data-engineering/trigger-table-sync-from-job/m-p/132860#M49658</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/9268"&gt;@Malthe&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;The recommended method is to manage and trigger the sync via table-level APIs or management interfaces, not the pipeline-level job triggers:&lt;/P&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;For Unity Catalog synced tables (e.g., syncing to Postgres), triggering a sync or refresh is performed by interacting with the table’s own API endpoint rather than the pipeline overview, such as using the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;CODE&gt;refresh&lt;/CODE&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;API or a manual command at the table level.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;If using the Unity Catalog or related table management system, you can issue an API call or use the Databricks CLI to manually trigger a sync (refresh), schedule triggers, or monitor the status of the ingest process at the table level.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;This design separates table sync pipelines from user-managed job pipelines to ensure that ingestion is strictly controlled via the target table’s management UI/API, maintaining data integrity and reliability.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;If your use case demands automated or programmatic triggering (for instance, after upstream data changes), it’s best practice to:&lt;/P&gt;
&lt;UL class="marker:text-quiet list-disc"&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Use the synced table’s refresh API endpoint in your automation/orchestration tools.&lt;/P&gt;
&lt;/LI&gt;
&lt;LI class="py-0 my-0 prose-p:pt-0 prose-p:mb-2 prose-p:my-0 [&amp;amp;&amp;gt;p]:pt-0 [&amp;amp;&amp;gt;p]:mb-2 [&amp;amp;&amp;gt;p]:my-0"&gt;
&lt;P class="my-2 [&amp;amp;+p]:mt-4 [&amp;amp;_strong:has(+br)]:inline-block [&amp;amp;_strong:has(+br)]:pb-2"&gt;Monitor and manage ingestion through the table sync management interface, not the pipeline jobs dashboard.&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;For additional details please refer to the below doc&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.databricks.com/aws/en/dev-tools/ci-cd/best-practices" target="_blank"&gt;https://docs.databricks.com/aws/en/dev-tools/ci-cd/best-practices&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 23 Sep 2025 15:18:18 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/trigger-table-sync-from-job/m-p/132860#M49658</guid>
      <dc:creator>Saritha_S</dc:creator>
      <dc:date>2025-09-23T15:18:18Z</dc:date>
    </item>
  </channel>
</rss>

