<?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 Materialized views Refresh strategy in Triggerd vs Continuous DLT mode in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/materialized-views-refresh-strategy-in-triggerd-vs-continuous/m-p/54190#M30008</link>
    <description>&lt;P&gt;Does Materialized views gets completely recalculated when we trigger DLT pipeline? Can't we start from where it left?&lt;BR /&gt;In continuous mode of DLT pipeline&amp;nbsp;Materialized view tries to optimizes the updates and computes the data?&lt;/P&gt;</description>
    <pubDate>Wed, 29 Nov 2023 10:04:02 GMT</pubDate>
    <dc:creator>ManojReddy</dc:creator>
    <dc:date>2023-11-29T10:04:02Z</dc:date>
    <item>
      <title>Materialized views Refresh strategy in Triggerd vs Continuous DLT mode</title>
      <link>https://community.databricks.com/t5/data-engineering/materialized-views-refresh-strategy-in-triggerd-vs-continuous/m-p/54190#M30008</link>
      <description>&lt;P&gt;Does Materialized views gets completely recalculated when we trigger DLT pipeline? Can't we start from where it left?&lt;BR /&gt;In continuous mode of DLT pipeline&amp;nbsp;Materialized view tries to optimizes the updates and computes the data?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Nov 2023 10:04:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/materialized-views-refresh-strategy-in-triggerd-vs-continuous/m-p/54190#M30008</guid>
      <dc:creator>ManojReddy</dc:creator>
      <dc:date>2023-11-29T10:04:02Z</dc:date>
    </item>
  </channel>
</rss>

