<?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 question of changing cluster key in liquid cluster in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/question-of-changing-cluster-key-in-liquid-cluster/m-p/72077#M34488</link>
    <description>&lt;P&gt;If i already have a cluster key1 for existing table, i want to change cluster key to key2 using&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;ALTER&lt;/SPAN&gt; &lt;SPAN&gt;TABLE&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;table CLUSTER &lt;/SPAN&gt;&lt;SPAN&gt;BY&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;(key2), then run&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;OPTIMIZE table&lt;/SPAN&gt;&lt;SPAN&gt;, based on databrick document , existing files will not be rewritten (verified by my test as well), cluster Key2 will only be applied incrementally.&amp;nbsp; If my existing files are huge (saying having long history), using Key2 will not improve performance when i search the table (e.g. select * from table where key2='xxxx'). is liquid cluster supposed to work this way or i am missing anything?&lt;/SPAN&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 07 Jun 2024 16:30:48 GMT</pubDate>
    <dc:creator>yj940525</dc:creator>
    <dc:date>2024-06-07T16:30:48Z</dc:date>
    <item>
      <title>question of changing cluster key in liquid cluster</title>
      <link>https://community.databricks.com/t5/data-engineering/question-of-changing-cluster-key-in-liquid-cluster/m-p/72077#M34488</link>
      <description>&lt;P&gt;If i already have a cluster key1 for existing table, i want to change cluster key to key2 using&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;SPAN&gt;ALTER&lt;/SPAN&gt; &lt;SPAN&gt;TABLE&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;table CLUSTER &lt;/SPAN&gt;&lt;SPAN&gt;BY&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;(key2), then run&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;OPTIMIZE table&lt;/SPAN&gt;&lt;SPAN&gt;, based on databrick document , existing files will not be rewritten (verified by my test as well), cluster Key2 will only be applied incrementally.&amp;nbsp; If my existing files are huge (saying having long history), using Key2 will not improve performance when i search the table (e.g. select * from table where key2='xxxx'). is liquid cluster supposed to work this way or i am missing anything?&lt;/SPAN&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 07 Jun 2024 16:30:48 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/question-of-changing-cluster-key-in-liquid-cluster/m-p/72077#M34488</guid>
      <dc:creator>yj940525</dc:creator>
      <dc:date>2024-06-07T16:30:48Z</dc:date>
    </item>
  </channel>
</rss>

