<?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: Handling files used more than once in a streaming pipeline in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/handling-files-used-more-than-once-in-a-streaming-pipeline/m-p/57397#M30769</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;It sounds like your Structured Streaming source is S3, in which case the easiest solution is likely to manage the stream source using an S3 Lifecycle Configuration (&lt;A href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)" target="_blank" rel="noopener"&gt;https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)&lt;/A&gt;. The objects could be managed by S3 Lifecycle via time-based trigger (e.g. 14 days) or it could&amp;nbsp; be more granularly managed using tags such that after a file is processed, you call the AWS SDK, tag an object with a key/value pair such as `delete=true` and then the lifecycle cleans up objects with those tags.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Tue, 16 Jan 2024 02:24:06 GMT</pubDate>
    <dc:creator>brockb</dc:creator>
    <dc:date>2024-01-16T02:24:06Z</dc:date>
    <item>
      <title>Handling files used more than once in a streaming pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/handling-files-used-more-than-once-in-a-streaming-pipeline/m-p/56816#M30658</link>
      <description>&lt;P&gt;I am implementing Structured Streaming using Delta Live Table. I want to delete the parquet files once they are used. What options should I set so that the files loaded in S3 are not deleted?&lt;/P&gt;</description>
      <pubDate>Tue, 09 Jan 2024 23:57:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/handling-files-used-more-than-once-in-a-streaming-pipeline/m-p/56816#M30658</guid>
      <dc:creator>rt-slowth</dc:creator>
      <dc:date>2024-01-09T23:57:52Z</dc:date>
    </item>
    <item>
      <title>Re: Handling files used more than once in a streaming pipeline</title>
      <link>https://community.databricks.com/t5/data-engineering/handling-files-used-more-than-once-in-a-streaming-pipeline/m-p/57397#M30769</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;It sounds like your Structured Streaming source is S3, in which case the easiest solution is likely to manage the stream source using an S3 Lifecycle Configuration (&lt;A href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)" target="_blank" rel="noopener"&gt;https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-lifecycle-mgmt.html)&lt;/A&gt;. The objects could be managed by S3 Lifecycle via time-based trigger (e.g. 14 days) or it could&amp;nbsp; be more granularly managed using tags such that after a file is processed, you call the AWS SDK, tag an object with a key/value pair such as `delete=true` and then the lifecycle cleans up objects with those tags.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 16 Jan 2024 02:24:06 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/handling-files-used-more-than-once-in-a-streaming-pipeline/m-p/57397#M30769</guid>
      <dc:creator>brockb</dc:creator>
      <dc:date>2024-01-16T02:24:06Z</dc:date>
    </item>
  </channel>
</rss>

