<?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: [Deprecation Marker Required] : MERGE INTO Clause in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/deprecation-marker-required-merge-into-clause/m-p/106120#M42390</link>
    <description>&lt;P&gt;Hello &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/142429"&gt;@Gajju&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;MERGE INTO is not being deprecated, APPLY CHANGES should be seen as an enhanced merge process in Delta Live Table that handles out of sequence records automatically as shown in&amp;nbsp; the example in the documentation shared.&lt;/P&gt;
&lt;P&gt;The notion of wrong results is pertaining to handling out of sequence records which may be prone to errors due to logic implementation in MERGE INTO&lt;/P&gt;
&lt;P&gt;MERGE wins when you you need full control of out of sequence without built-in sequencing feature use cases&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
    <pubDate>Fri, 17 Jan 2025 16:22:54 GMT</pubDate>
    <dc:creator>User16502773013</dc:creator>
    <dc:date>2025-01-17T16:22:54Z</dc:date>
    <item>
      <title>[Deprecation Marker Required] : MERGE INTO Clause</title>
      <link>https://community.databricks.com/t5/data-engineering/deprecation-marker-required-merge-into-clause/m-p/106046#M42366</link>
      <description>&lt;P&gt;Dear Friends:&lt;/P&gt;&lt;P&gt;Considering MERGE INTO may generate wrong results(&lt;A href="https://docs.databricks.com/en/delta-live-tables/cdc.html" target="_blank"&gt;The APPLY CHANGES APIs: Simplify change data capture with Delta Live Tables | Databricks on AWS&lt;/A&gt;), may I ask that why it's API is still floating in technical documentation, without "Deprecated/Obsolete Marker" ?&lt;/P&gt;&lt;P&gt;It's causing confusion.&lt;/P&gt;&lt;P&gt;Is there any use case where MERGE wins over APPLY CHANGES INTO?&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2025 09:49:43 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/deprecation-marker-required-merge-into-clause/m-p/106046#M42366</guid>
      <dc:creator>Gajju</dc:creator>
      <dc:date>2025-01-17T09:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: [Deprecation Marker Required] : MERGE INTO Clause</title>
      <link>https://community.databricks.com/t5/data-engineering/deprecation-marker-required-merge-into-clause/m-p/106120#M42390</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/142429"&gt;@Gajju&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;MERGE INTO is not being deprecated, APPLY CHANGES should be seen as an enhanced merge process in Delta Live Table that handles out of sequence records automatically as shown in&amp;nbsp; the example in the documentation shared.&lt;/P&gt;
&lt;P&gt;The notion of wrong results is pertaining to handling out of sequence records which may be prone to errors due to logic implementation in MERGE INTO&lt;/P&gt;
&lt;P&gt;MERGE wins when you you need full control of out of sequence without built-in sequencing feature use cases&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2025 16:22:54 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/deprecation-marker-required-merge-into-clause/m-p/106120#M42390</guid>
      <dc:creator>User16502773013</dc:creator>
      <dc:date>2025-01-17T16:22:54Z</dc:date>
    </item>
  </channel>
</rss>

