# Deletion vectors

Glossary, read 10 Nov 2026

**The short answer.** Deletion vectors mark rows as deleted or modified in table metadata instead of rewriting the Parquet file that holds them. Readers apply the marks at query time. Databricks documents them for Delta Lake and Iceberg tables, and the Iceberg specification adopted them as its row-level delete representation in format v3.

Without them, changing one row means rewriting the whole file containing it. With them, a DELETE, UPDATE or MERGE writes a small bitmap, and a later OPTIMIZE or compaction rewrites the file.

Support is by engine and version, so a table written with deletion vectors may not be readable by an older client.

## A sourced example

Databricks's page, last updated Nov 6, 2026, says Iceberg v3 tables include deletion vectors by default, Delta tables need them enabled explicitly, and reading them needs Runtime 12.2 LTS or above.

## Sources

- Deletion vectors in Databricks: https://docs.databricks.com/aws/en/delta/deletion-vectors (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://datalakehousecompare.com/glossary/deletion-vectors/
