<?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: Vacuum on DLT in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142523#M51964</link>
    <description>&lt;P&gt;Hi, you shouldn't need to run these manually; they will automatically run as part of the liquid clustering, and in fact, it is actively discouraged to run them manually.&lt;/P&gt;</description>
    <pubDate>Wed, 24 Dec 2025 12:08:12 GMT</pubDate>
    <dc:creator>emma_s</dc:creator>
    <dc:date>2025-12-24T12:08:12Z</dc:date>
    <item>
      <title>Vacuum on DLT</title>
      <link>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142512#M51962</link>
      <description>&lt;P&gt;We are currently using DLT tables in our target tables. The tables are getting loaded in continuous job pipelines.&lt;/P&gt;&lt;P&gt;The liquid cluster is enabled in the tables. Will Vacuum work on these tables when it is getting loaded in continuous mode? How to run the vacuum without impacting the checkpoints and the actual load of the DLT tables?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Dec 2025 09:59:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142512#M51962</guid>
      <dc:creator>JothyGanesan</dc:creator>
      <dc:date>2025-12-24T09:59:46Z</dc:date>
    </item>
    <item>
      <title>Re: Vacuum on DLT</title>
      <link>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142523#M51964</link>
      <description>&lt;P&gt;Hi, you shouldn't need to run these manually; they will automatically run as part of the liquid clustering, and in fact, it is actively discouraged to run them manually.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Dec 2025 12:08:12 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142523#M51964</guid>
      <dc:creator>emma_s</dc:creator>
      <dc:date>2025-12-24T12:08:12Z</dc:date>
    </item>
    <item>
      <title>Re: Vacuum on DLT</title>
      <link>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142533#M51966</link>
      <description>&lt;P&gt;VACUUM works fine on DLT tables running in continuous mode. DLT does automatic maintenance (OPTIMIZE + VACUUM) roughly every 24 hours if the pipeline has a maintenance cluster configured.&lt;/P&gt;
&lt;P&gt;Q: The liquid cluster is enabled in the tables. Will Vacuum work on these tables when it is getting loaded in continuous mode? How to run the vacuum without impacting the checkpoints and the actual load of the DLT tables?&lt;BR /&gt;A:&amp;nbsp;It won’t mess with checkpoints: VACUUM only removes orphaned data files and skips special dirs like _delta_log; DLT manages streaming checkpoints separately under the pipeline storage .../checkpoints/. Keep retention ≥ 7 days to stay safe.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Dec 2025 15:23:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/vacuum-on-dlt/m-p/142533#M51966</guid>
      <dc:creator>iyashk-DB</dc:creator>
      <dc:date>2025-12-24T15:23:11Z</dc:date>
    </item>
  </channel>
</rss>

