<?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 DLT File Level Deduplication in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/dlt-file-level-deduplication/m-p/141894#M51845</link>
    <description>&lt;P&gt;I want to create a DLT pipeline that incrementally processes csv files arriving daily. However, some of those files are duplicate - they have the same names and data but are in different directories. What is the best way to handle this? I'm assuming that row-level deduplication would be inefficient, but not sure if file-level deduplication is possible with DLT streaming.&lt;/P&gt;</description>
    <pubDate>Mon, 15 Dec 2025 19:01:20 GMT</pubDate>
    <dc:creator>dgahram</dc:creator>
    <dc:date>2025-12-15T19:01:20Z</dc:date>
    <item>
      <title>DLT File Level Deduplication</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-file-level-deduplication/m-p/141894#M51845</link>
      <description>&lt;P&gt;I want to create a DLT pipeline that incrementally processes csv files arriving daily. However, some of those files are duplicate - they have the same names and data but are in different directories. What is the best way to handle this? I'm assuming that row-level deduplication would be inefficient, but not sure if file-level deduplication is possible with DLT streaming.&lt;/P&gt;</description>
      <pubDate>Mon, 15 Dec 2025 19:01:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-file-level-deduplication/m-p/141894#M51845</guid>
      <dc:creator>dgahram</dc:creator>
      <dc:date>2025-12-15T19:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: DLT File Level Deduplication</title>
      <link>https://community.databricks.com/t5/data-engineering/dlt-file-level-deduplication/m-p/141911#M51850</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/200917"&gt;@dgahram&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI data-start="321" data-end="559"&gt;
&lt;P data-start="323" data-end="559"&gt;Auto Loader tracks ingestion progress by persisting discovered file metadata in a &lt;STRONG data-start="405" data-end="444"&gt;RocksDB store&amp;nbsp;&lt;/STRONG&gt;&lt;SPAN&gt;&lt;STRONG&gt;within the checkpoint&lt;/STRONG&gt;, which provides “&lt;/SPAN&gt;exactly-once” processing for &lt;EM data-start="500" data-end="518"&gt;discovered files&lt;/EM&gt;.&lt;STRONG&gt;Doc&lt;/STRONG&gt;:&amp;nbsp;&lt;A href="https://docs.databricks.com/aws/en/ingestion/cloud-object-storage/auto-loader/" target="_blank"&gt;https://docs.databricks.com/aws/en/ingestion/cloud-object-storage/auto-loader/&lt;/A&gt;&lt;/P&gt;
&lt;/LI&gt;
&lt;LI data-start="560" data-end="790"&gt;
&lt;P data-start="562" data-end="790"&gt;&lt;SPAN&gt;However, if the&amp;nbsp;&lt;/SPAN&gt;&lt;EM style="color: #183139;"&gt;same content&lt;/EM&gt;&lt;SPAN&gt;&amp;nbsp;appears under&lt;/SPAN&gt;&amp;nbsp;&lt;STRONG data-start="600" data-end="624"&gt;different file paths&lt;/STRONG&gt; (for example, duplicated into another directory), Auto Loader will still “discover” it as a new file and ingest it (because it is, from a file-discovery standpoint).&lt;/P&gt;
&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;In DLT, there is also no option for file deduplication. The best practice is to file de-dupe&amp;nbsp;&lt;STRONG data-start="3947" data-end="3957"&gt;before&lt;/STRONG&gt; DLT ingestion.&amp;nbsp;Inside streaming, “file-level dedup” is awkward because the stream is already row-oriented after CSV parsing.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2025 02:20:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/dlt-file-level-deduplication/m-p/141911#M51850</guid>
      <dc:creator>K_Anudeep</dc:creator>
      <dc:date>2025-12-16T02:20:20Z</dc:date>
    </item>
  </channel>
</rss>

