# Schema evolution

Glossary, read 10 Nov 2026

**The short answer.** Schema evolution is changing a table's columns without rewriting its data. Iceberg supports add, drop, rename, update (type widening) and reorder, including inside nested structs, as metadata-only changes that never make an existing column read another column's values. Engines differ in which changes they expose in SQL.

Iceberg says schema changes are independent and free of side effects: an added column never reads another column's values, and dropping or updating a column changes no other column.

Delta Lake and Hudi support schema changes too, with their own rules for column mapping and type changes. Check the exact operation against the engine and version you run.

## A sourced example

The Iceberg evolution page says that moving a Hive table from a daily to an hourly layout needs a new table, and that even renaming a column is unsupported or unsafe in some older table formats.

## 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/schema-evolution/
