<?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 A Surprise Findings in Delta Live Table in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/a-surprise-findings-in-delta-live-table/m-p/84438#M37194</link>
    <description>&lt;P&gt;While DLT has some powerful features, I found myself doing a double-take when I realized it doesn’t natively support hard deletes. Instead, it leans on a delete flag identifier to manage these in the source table. A bit surprising for a tool of its caliber, don’t you think?&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/5"&gt;@Sujitha&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let's pass it on to all Databricks Community User&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2024 15:14:12 GMT</pubDate>
    <dc:creator>CURIOUS_DE</dc:creator>
    <dc:date>2024-08-27T15:14:12Z</dc:date>
    <item>
      <title>A Surprise Findings in Delta Live Table</title>
      <link>https://community.databricks.com/t5/data-engineering/a-surprise-findings-in-delta-live-table/m-p/84438#M37194</link>
      <description>&lt;P&gt;While DLT has some powerful features, I found myself doing a double-take when I realized it doesn’t natively support hard deletes. Instead, it leans on a delete flag identifier to manage these in the source table. A bit surprising for a tool of its caliber, don’t you think?&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/5"&gt;@Sujitha&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Let's pass it on to all Databricks Community User&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2024 15:14:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/a-surprise-findings-in-delta-live-table/m-p/84438#M37194</guid>
      <dc:creator>CURIOUS_DE</dc:creator>
      <dc:date>2024-08-27T15:14:12Z</dc:date>
    </item>
    <item>
      <title>Re: A Surprise Findings in Delta Live Table</title>
      <link>https://community.databricks.com/t5/data-engineering/a-surprise-findings-in-delta-live-table/m-p/103339#M41408</link>
      <description>&lt;P&gt;Thanks for your feedback !&lt;/P&gt;
&lt;P&gt;I believe,&amp;nbsp;Delta Live Tables (DLT) does not natively support hard deletes and instead uses a delete flag identifier to manage deletions, a design choice rooted in ensuring compliance with regulations like GDPR and CCPA. This approach facilitates traceability, auditing, and the &lt;STRONG&gt;"Right to be Forgotten",&lt;/STRONG&gt; avoiding the complexities and risks of immediate hard deletes in large-scale data environments. Additionally, it leverages Delta Lake’s time travel and retention features to maintain data integrity, support recovery, and prevent disruptions to downstream pipelines, striking a balance between governance, compliance, and operational reliability.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.databricks.com/blog/handling-right-be-forgotten-gdpr-and-ccpa-using-delta-live-tables-dlt" target="_blank"&gt;https://www.databricks.com/blog/handling-right-be-forgotten-gdpr-and-ccpa-using-delta-live-tables-dlt&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Dec 2024 18:13:14 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/a-surprise-findings-in-delta-live-table/m-p/103339#M41408</guid>
      <dc:creator>VZLA</dc:creator>
      <dc:date>2024-12-27T18:13:14Z</dc:date>
    </item>
  </channel>
</rss>

