<?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 Handling GDPR requests in databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/handling-gdpr-requests-in-databricks/m-p/42571#M27407</link>
    <description>&lt;P&gt;When dealing with GDPR requests in &lt;STRONG&gt;databricks&lt;/STRONG&gt;, there are some essential things to keep in mind:&lt;/P&gt;&lt;P&gt;- Use a low retention period to ensure you don't keep table delta version history for tables with personal information.&lt;/P&gt;&lt;P&gt;- Use APPLY CHANGES to handle Slowly Changing Dimension type 1. This way, you won't track history (like in type 2) and will have it in a separate table.&lt;/P&gt;&lt;P&gt;- When handling customer insertion and GDPR requests, use a changed data feed in databricks. Ensure the table is declared as LIVE, not STREAM, to ensure complete data reload and avoid records for which we have received GDPR requests.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ezgif-3-020e69a4fd.gif" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/3289iB30A84A4506D97CB/image-size/large?v=v2&amp;amp;px=999" role="button" title="ezgif-3-020e69a4fd.gif" alt="ezgif-3-020e69a4fd.gif" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 28 Aug 2023 17:01:37 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2023-08-28T17:01:37Z</dc:date>
    <item>
      <title>Handling GDPR requests in databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/handling-gdpr-requests-in-databricks/m-p/42571#M27407</link>
      <description>&lt;P&gt;When dealing with GDPR requests in &lt;STRONG&gt;databricks&lt;/STRONG&gt;, there are some essential things to keep in mind:&lt;/P&gt;&lt;P&gt;- Use a low retention period to ensure you don't keep table delta version history for tables with personal information.&lt;/P&gt;&lt;P&gt;- Use APPLY CHANGES to handle Slowly Changing Dimension type 1. This way, you won't track history (like in type 2) and will have it in a separate table.&lt;/P&gt;&lt;P&gt;- When handling customer insertion and GDPR requests, use a changed data feed in databricks. Ensure the table is declared as LIVE, not STREAM, to ensure complete data reload and avoid records for which we have received GDPR requests.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ezgif-3-020e69a4fd.gif" style="width: 999px;"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/3289iB30A84A4506D97CB/image-size/large?v=v2&amp;amp;px=999" role="button" title="ezgif-3-020e69a4fd.gif" alt="ezgif-3-020e69a4fd.gif" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Aug 2023 17:01:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/handling-gdpr-requests-in-databricks/m-p/42571#M27407</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2023-08-28T17:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: Handling GDPR requests in databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/handling-gdpr-requests-in-databricks/m-p/42894#M27443</link>
      <description>&lt;P&gt;Thank you for sharing this information&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/25346"&gt;@Hubert-Dudek&lt;/a&gt;!!!!&lt;/P&gt;</description>
      <pubDate>Wed, 30 Aug 2023 17:26:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/handling-gdpr-requests-in-databricks/m-p/42894#M27443</guid>
      <dc:creator>jose_gonzalez</dc:creator>
      <dc:date>2023-08-30T17:26:29Z</dc:date>
    </item>
  </channel>
</rss>

