1 rollouts.storage.repack

rollouts.storage.repack

Lossless layout-only rollout rewriting with unchanged source references.

Whole-store rechunking preserves every stored array and relationship. Chain merge/split and binding to physically rewritten roots require a separate coordinated transformation and are deliberately not implied by this interface.

1.1 Functions

Name Description
rechunk_rollout_store Copy a validated rollout store into a fresh physical read-chunk layout.

1.1.1 rechunk_rollout_store

rollouts.storage.repack.rechunk_rollout_store(
    source,
    destination,
    *,
    array_chunks,
)

Copy a validated rollout store into a fresh physical read-chunk layout.

Array paths and shapes, exact dtypes/values, dictionary IDs, masks, chain and successor foreign keys, optional observations/crops and source bindings are conserved without regeneration or relabeling. Unspecified arrays retain their chunks. Overrides must name present arrays and have positive matching rank. Existing internal Zarr storage sharding is unsupported and rejects explicitly.

A derived manifest authenticates the source inventory and chunk overrides; the original acquisition manifest and all sidecars remain available verbatim. Canonical validation and source-currentness checks precede atomic promotion. Failures never publish a partial destination. Source references still require the unchanged original roots; this operation does not remap them.

Back to top