Skip to content
Lakehouse Compare

Glossary, read 10 Nov 2026

Partition evolution

All termsOpen the Compute Bill

Because queries do not reference partition values directly, no query has to be rewritten when the spec changes.

The cost is that old and new layouts coexist until you rewrite old files. Databricks liquid clustering addresses the same need by letting you redefine clustering keys without rewriting existing data.

A sourced example

The Iceberg evolution page says metadata for each partition version is kept separately, so a query against a table with two specs gets split planning, with each layout planning its files using the filter it derives.

Sources

  1. Iceberg documentation: evolution, read 10 Nov 2026

Last reviewed 10 Nov 2026.