{
  "status": "shipping",
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-23",
  "advantages": [],
  "limitations": [],
  "slug": "zarr-consolidated-metadata",
  "term": "Zarr consolidated metadata",
  "aliases": [],
  "definition": "Zarr consolidated metadata collects metadata for a hierarchy into a consolidated representation to reduce separate metadata reads.",
  "note": "Purpose: consolidation reduces metadata requests, especially for hierarchies on high-latency storage. It does not itself capture chunk values as a dataset snapshot. [zarr-consolidation]\n\nFreshness: 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. [zarr-consolidation]\n\nMeasured 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. [hesela-zarr]",
  "related": [
    "zarr",
    "zarr-fill-value",
    "backup-verification"
  ],
  "citations": [
    {
      "id": "zarr-consolidation",
      "title": "Zarr-Python: consolidated metadata and synchronization",
      "url": "https://zarr.readthedocs.io/en/stable/user-guide/consolidated_metadata/",
      "accessed": "2026-10-23"
    },
    {
      "id": "hesela-zarr",
      "title": "Hesela: Zarr archive acceptance observations",
      "url": "https://hesela.dev/datasets/zarr-archive-acceptance/",
      "accessed": "2026-10-23"
    }
  ]
}