# Partition evolution

Glossary, read 10 Nov 2026

**The short answer.** Partition evolution changes how an existing table is partitioned without rewriting old data. In Iceberg, files written under an earlier partition spec stay as they are, new data uses the new layout, and the planner splits each query across the layouts. A team can move from daily to hourly partitions in place.

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

- Iceberg documentation: evolution: https://iceberg.apache.org/docs/latest/evolution/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/glossary/partition-evolution/
