<?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 Triggering  clean-ups in Spark to handle accumulated metadata in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/triggering-clean-ups-in-spark-to-handle-accumulated-metadata/m-p/19631#M13185</link>
    <description />
    <pubDate>Fri, 25 Jun 2021 15:48:50 GMT</pubDate>
    <dc:creator>User16826994223</dc:creator>
    <dc:date>2021-06-25T15:48:50Z</dc:date>
    <item>
      <title>Triggering  clean-ups in Spark to handle accumulated metadata</title>
      <link>https://community.databricks.com/t5/data-engineering/triggering-clean-ups-in-spark-to-handle-accumulated-metadata/m-p/19631#M13185</link>
      <description />
      <pubDate>Fri, 25 Jun 2021 15:48:50 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/triggering-clean-ups-in-spark-to-handle-accumulated-metadata/m-p/19631#M13185</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-25T15:48:50Z</dc:date>
    </item>
    <item>
      <title>Re: Triggering  clean-ups in Spark to handle accumulated metadata</title>
      <link>https://community.databricks.com/t5/data-engineering/triggering-clean-ups-in-spark-to-handle-accumulated-metadata/m-p/19632#M13186</link>
      <description>&lt;P&gt; setting the parameter ‘spark.cleaner.ttl’ or by dividing the long running jobs into different batches and writing the intermediary results to the disk.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jun 2021 15:49:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/triggering-clean-ups-in-spark-to-handle-accumulated-metadata/m-p/19632#M13186</guid>
      <dc:creator>User16826994223</dc:creator>
      <dc:date>2021-06-25T15:49:20Z</dc:date>
    </item>
  </channel>
</rss>

