<?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: DLT Apply Changes in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94163#M38829</link>
    <description>&lt;P data-unlink="true"&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/31201"&gt;@ankitmit&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;If you check &lt;A href="https://docs.databricks.com/en/delta-live-tables/sql-ref.html#cdc" target="_self"&gt;the documentation of APPLY CHANGES&lt;/A&gt;, there is no parameter to exclude the column from being updated.&lt;BR /&gt;&lt;BR /&gt;As you noticed, columns parameter is used to specify the columns included in the target table, so excluding created_table, means the column will not be available in the target table.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 15 Oct 2024 16:28:02 GMT</pubDate>
    <dc:creator>filipniziol</dc:creator>
    <dc:date>2024-10-15T16:28:02Z</dc:date>
    <item>
      <title>DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94121#M38816</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;In DLT, how do we specify which columns we don't want to overwrite when using the “apply changes” operation in the DLT (in the attached example, we want to avoid overwriting the “created_time” column)?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I am using this sample code&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;dlt.&lt;/SPAN&gt;&lt;SPAN&gt;apply_changes&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;source&lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;f&lt;/SPAN&gt;&lt;SPAN&gt;"&lt;/SPAN&gt;&lt;SPAN&gt;{&lt;/SPAN&gt;&lt;SPAN&gt;table_name&lt;/SPAN&gt;&lt;SPAN&gt;}&lt;/SPAN&gt;&lt;SPAN&gt;_cdc"&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;target&lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; table_name,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;keys&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; table_keys,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;sequence_by&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; F.&lt;/SPAN&gt;&lt;SPAN&gt;col&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;'_fivetran_synced'&lt;/SPAN&gt;&lt;SPAN&gt;),&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;except_column_list&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt; [&lt;/SPAN&gt;&lt;SPAN&gt;'created_time'&lt;/SPAN&gt;&lt;SPAN&gt;],&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;stored_as_scd_type&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;1&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;apply_as_deletes&lt;/SPAN&gt;&lt;SPAN&gt;=&lt;/SPAN&gt;&lt;SPAN&gt;F.&lt;/SPAN&gt;&lt;SPAN&gt;expr&lt;/SPAN&gt;&lt;SPAN&gt;(&lt;/SPAN&gt;&lt;SPAN&gt;"_fivetran_deleted= true"&lt;/SPAN&gt;&lt;SPAN&gt;),&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;track_history_column_list&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;None&lt;/SPAN&gt;&lt;SPAN&gt;,&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;track_history_except_column_list&lt;/SPAN&gt; &lt;SPAN&gt;=&lt;/SPAN&gt; &lt;SPAN&gt;None&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;)&lt;BR /&gt;&lt;BR /&gt;But instead,&amp;nbsp;except_column_list drops this column from the target table.&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 15 Oct 2024 14:05:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94121#M38816</guid>
      <dc:creator>ankitmit</dc:creator>
      <dc:date>2024-10-15T14:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94163#M38829</link>
      <description>&lt;P data-unlink="true"&gt;Hi&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/31201"&gt;@ankitmit&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;&lt;BR /&gt;If you check &lt;A href="https://docs.databricks.com/en/delta-live-tables/sql-ref.html#cdc" target="_self"&gt;the documentation of APPLY CHANGES&lt;/A&gt;, there is no parameter to exclude the column from being updated.&lt;BR /&gt;&lt;BR /&gt;As you noticed, columns parameter is used to specify the columns included in the target table, so excluding created_table, means the column will not be available in the target table.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 16:28:02 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94163#M38829</guid>
      <dc:creator>filipniziol</dc:creator>
      <dc:date>2024-10-15T16:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94164#M38830</link>
      <description>&lt;P&gt;There might be a misunderstanding regarding the except_column_list parameter in the apply_changes function. This parameter is used to specify which columns to exclude from the changes, but in this case, it seems like it’s dropping the created_time column instead of preserving it.&lt;/P&gt;&lt;P&gt;One approach to consider is ensuring that the data types and configurations are compatible with the intended functionality.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 16:29:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/94164#M38830</guid>
      <dc:creator>Finn-Ol</dc:creator>
      <dc:date>2024-10-15T16:29:00Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/95648#M39138</link>
      <description>&lt;P&gt;Yes, that's exactly the problem.&amp;nbsp;&lt;SPAN&gt;except_column_list is dropping the column from the target table instead of excluding them from the changes.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Oct 2024 06:53:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/95648#M39138</guid>
      <dc:creator>ankitmit</dc:creator>
      <dc:date>2024-10-23T06:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/97875#M39567</link>
      <description>&lt;P&gt;I am facing a similar issue. Is there any solution to select which columns to update when using "apply changes" operation?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Nov 2024 08:50:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/97875#M39567</guid>
      <dc:creator>HoussemBL</dc:creator>
      <dc:date>2024-11-06T08:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/107913#M42945</link>
      <description>&lt;P&gt;&lt;SPAN&gt;In my case, 3 files were loaded at same time which has records with same keys but increasing sequence by value. I added date column in&amp;nbsp;track_history_except_column_list in order to avoid tracking of history but values of date column came different for all records. Can anyone explain why this is happening?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2025 19:04:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/107913#M42945</guid>
      <dc:creator>Anish_2</dc:creator>
      <dc:date>2025-01-30T19:04:39Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/118604#M45663</link>
      <description>&lt;P&gt;I'm experience same issue where the columns added to except_column_list are being dropped instead of ignored.&lt;/P&gt;</description>
      <pubDate>Fri, 09 May 2025 01:09:27 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/118604#M45663</guid>
      <dc:creator>juice</dc:creator>
      <dc:date>2025-05-09T01:09:27Z</dc:date>
    </item>
    <item>
      <title>Re: DLT Apply Changes</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/122749#M46856</link>
      <description>&lt;P&gt;Same here, it's kinda ridiculous that apply_changes doesn't support a parameter to update certain columns... how come that is not a priority since this was released?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 23:48:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-apply-changes/m-p/122749#M46856</guid>
      <dc:creator>brunoillipronti</dc:creator>
      <dc:date>2025-06-24T23:48:58Z</dc:date>
    </item>
  </channel>
</rss>

