<?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: Getting started with Delta Lake basics in Genie Hub</title>
    <link>https://community.databricks.com/t5/genie-hub/getting-started-with-delta-lake-basics/m-p/168379#M60</link>
    <description>&lt;P&gt;Did you forgot to share the short note?&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;If you are referring to running optimize after Merge, its worth mentioning that it doesn't need to be run after every Merge.&lt;/P&gt;&lt;P&gt;MERGE can create or rewrite files, but whether OPTIMIZE is needed immediately depends on the table size, write frequency, file layout, and query pattern. For frequently updated tables, its better to avoid.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Better options are&lt;/STRONG&gt;:&amp;nbsp;Databricks can already reduce small-file issues with optimized writes and auto compaction.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ALTER TABLE catalog.schema.table_name
SET TBLPROPERTIES (
  delta.autoOptimize.optimizeWrite = true,
  delta.autoOptimize.autoCompact = true
);&lt;/LI-CODE&gt;&lt;P&gt;Then use &lt;STRONG&gt;OPTIMIZE&lt;/STRONG&gt; based on actual file/query behavior or let &lt;STRONG&gt;Predictive Optimization&lt;/STRONG&gt; manage maintenance automatically for UC managed tables. &lt;A href="https://docs.databricks.com/aws/en/tables/tune-file-size" target="_self"&gt;Reference&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 11 Sep 2026 15:17:00 GMT</pubDate>
    <dc:creator>data_pulse</dc:creator>
    <dc:date>2026-09-11T15:17:00Z</dc:date>
    <item>
      <title>Getting started with Delta Lake basics</title>
      <link>https://community.databricks.com/t5/genie-hub/getting-started-with-delta-lake-basics/m-p/168367#M59</link>
      <description>Hi all — I am working through the Delta Lake intro and wanted to share a short note on using OPTIMIZE after merge. Happy to hear better patterns.</description>
      <pubDate>Fri, 11 Sep 2026 13:29:58 GMT</pubDate>
      <guid>https://community.databricks.com/t5/genie-hub/getting-started-with-delta-lake-basics/m-p/168367#M59</guid>
      <dc:creator>rachelnguyen</dc:creator>
      <dc:date>2026-09-11T13:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Getting started with Delta Lake basics</title>
      <link>https://community.databricks.com/t5/genie-hub/getting-started-with-delta-lake-basics/m-p/168379#M60</link>
      <description>&lt;P&gt;Did you forgot to share the short note?&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;If you are referring to running optimize after Merge, its worth mentioning that it doesn't need to be run after every Merge.&lt;/P&gt;&lt;P&gt;MERGE can create or rewrite files, but whether OPTIMIZE is needed immediately depends on the table size, write frequency, file layout, and query pattern. For frequently updated tables, its better to avoid.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Better options are&lt;/STRONG&gt;:&amp;nbsp;Databricks can already reduce small-file issues with optimized writes and auto compaction.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;ALTER TABLE catalog.schema.table_name
SET TBLPROPERTIES (
  delta.autoOptimize.optimizeWrite = true,
  delta.autoOptimize.autoCompact = true
);&lt;/LI-CODE&gt;&lt;P&gt;Then use &lt;STRONG&gt;OPTIMIZE&lt;/STRONG&gt; based on actual file/query behavior or let &lt;STRONG&gt;Predictive Optimization&lt;/STRONG&gt; manage maintenance automatically for UC managed tables. &lt;A href="https://docs.databricks.com/aws/en/tables/tune-file-size" target="_self"&gt;Reference&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2026 15:17:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/genie-hub/getting-started-with-delta-lake-basics/m-p/168379#M60</guid>
      <dc:creator>data_pulse</dc:creator>
      <dc:date>2026-09-11T15:17:00Z</dc:date>
    </item>
  </channel>
</rss>

