<?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 How is the ETL process different than  trigger once stream in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/how-is-the-etl-process-different-than-trigger-once-stream/m-p/23390#M16135</link>
    <description>&lt;P&gt;I am little confused between what to use between structured stream(trigger once) and etl batch jobs, can I get help here  on which basis i should make my decision.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Jun 2021 07:54:41 GMT</pubDate>
    <dc:creator>User16826994223</dc:creator>
    <dc:date>2021-06-17T07:54:41Z</dc:date>
    <item>
      <title>How is the ETL process different than  trigger once stream</title>
      <link>https://community.databricks.com/t5/data-engineering/how-is-the-etl-process-different-than-trigger-once-stream/m-p/23390#M16135</link>
      <description>&lt;P&gt;I am little confused between what to use between structured stream(trigger once) and etl batch jobs, can I get help here  on which basis i should make my decision.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 07:54:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-is-the-etl-process-different-than-trigger-once-stream/m-p/23390#M16135</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-17T07:54:41Z</dc:date>
    </item>
    <item>
      <title>Re: How is the ETL process different than  trigger once stream</title>
      <link>https://community.databricks.com/t5/data-engineering/how-is-the-etl-process-different-than-trigger-once-stream/m-p/23391#M16136</link>
      <description>&lt;P&gt;In Structured Streaming, triggers are used to specify how often a streaming query should produce results. A RunOnce trigger will fire only once and then will stop the query - effectively running it like a batch job.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, If your source data is a streaming source, streaming and RunOnce is better than batch in general. Here is a blog post explaining this &lt;A href="https://databricks.com/blog/2017/05/22/running-streaming-jobs-day-10x-cost-savings.html" target="test_blank"&gt;https://databricks.com/blog/2017/05/22/running-streaming-jobs-day-10x-cost-savings.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 05:39:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-is-the-etl-process-different-than-trigger-once-stream/m-p/23391#M16136</guid>
      <dc:creator>sajith_appukutt</dc:creator>
      <dc:date>2021-06-23T05:39:50Z</dc:date>
    </item>
  </channel>
</rss>

