zarr-consolidated-metadata · shipping

Zarr consolidated metadata

Zarr consolidated metadata collects metadata for a hierarchy into a consolidated representation to reduce separate metadata reads.

Related Observatory article: Zarr consolidated metadata on hesela.com

Purpose: consolidation reduces metadata requests, especially for hierarchies on high-latency storage. It does not itself capture chunk values as a dataset snapshot. [1]

Freshness: metadata changes can make the consolidated representation stale; applications must coordinate publication and reader refresh with their update protocol. Bypassing consolidation does not establish an atomic multi-object snapshot. [1]

Measured boundary: in Hesela's ordered Zarr-Python 3.1.3 format-2 experiment, a stale consolidated reader saw an eight-element shape with a newly overwritten first value. A fresh unconsolidated reader saw twelve elements; re-consolidation did not refresh an already retained handle. This is version-scoped local evidence, not a format-3 concurrency result. [2]

Relations

related
Zarr, Zarr fill value, Backup verification

Citations

  1. Zarr-Python: consolidated metadata and synchronization (accessed 2026-10-23)
  2. Hesela: Zarr archive acceptance observations (accessed 2026-10-23)

JSON: /data/terms/zarr-consolidated-metadata.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Zarr consolidated metadata. Hesela. 2026-10-23. https://hesela.dev/terms/zarr-consolidated-metadata/