<?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 APPLY_CHANGES late arriving data in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/apply-changes-late-arriving-data/m-p/48669#M28357</link>
    <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I have a DLT pipeline that uses APPLY_CHANGES to our Silver tables.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Id as keys and timestamp to know the sequence of the incoming data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question: How does APPLY_CHANGES handles late arriving data?&lt;/P&gt;&lt;P&gt;i.e., for silver_table_1, the data comes for Id 1 at 08/10/2023 at 10:30pm. This record got inserted to silver_table_1. Next day, same Id 1 data arrives but the timestamp is 07/10/2023 at 08:00pm. As you can see the timestamp is different and is less than&amp;nbsp;from the inserted record.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;G&lt;/P&gt;</description>
    <pubDate>Sat, 07 Oct 2023 20:13:32 GMT</pubDate>
    <dc:creator>Gilg</dc:creator>
    <dc:date>2023-10-07T20:13:32Z</dc:date>
    <item>
      <title>APPLY_CHANGES late arriving data</title>
      <link>https://community.databricks.com/t5/data-engineering/apply-changes-late-arriving-data/m-p/48669#M28357</link>
      <description>&lt;P&gt;Hi Team,&lt;/P&gt;&lt;P&gt;I have a DLT pipeline that uses APPLY_CHANGES to our Silver tables.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am using Id as keys and timestamp to know the sequence of the incoming data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Question: How does APPLY_CHANGES handles late arriving data?&lt;/P&gt;&lt;P&gt;i.e., for silver_table_1, the data comes for Id 1 at 08/10/2023 at 10:30pm. This record got inserted to silver_table_1. Next day, same Id 1 data arrives but the timestamp is 07/10/2023 at 08:00pm. As you can see the timestamp is different and is less than&amp;nbsp;from the inserted record.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;G&lt;/P&gt;</description>
      <pubDate>Sat, 07 Oct 2023 20:13:32 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/apply-changes-late-arriving-data/m-p/48669#M28357</guid>
      <dc:creator>Gilg</dc:creator>
      <dc:date>2023-10-07T20:13:32Z</dc:date>
    </item>
    <item>
      <title>Re: APPLY_CHANGES late arriving data</title>
      <link>https://community.databricks.com/t5/data-engineering/apply-changes-late-arriving-data/m-p/48892#M28408</link>
      <description>&lt;P&gt;Hi Kaniz,&lt;/P&gt;&lt;P&gt;Will this work in SCD Type1 table? As I understand the&lt;STRONG&gt;&amp;nbsp;__START_AT&lt;/STRONG&gt; and &lt;STRONG&gt;__END_AT&lt;/STRONG&gt; columns are only available in SCD Type 2 APPLY_CHANGES. When I do a quick select of the table using SQL Warehouse I do not see these columns in a Type 1 table.&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;G&lt;/P&gt;</description>
      <pubDate>Tue, 10 Oct 2023 23:58:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/apply-changes-late-arriving-data/m-p/48892#M28408</guid>
      <dc:creator>Gilg</dc:creator>
      <dc:date>2023-10-10T23:58:50Z</dc:date>
    </item>
  </channel>
</rss>

