Hi everyone,

Context

I'm working on a data format built on top off zarr / using zarr for array and meta data storage.
Part of this involves the creation of a zarr hierarchy, writing arrays, metadata etc.
I would like to bundle them up into transactions, to ensure that I never arrive at an inconsistent state on failure (e.g. system crash).

Question

I was wondering on how to approach that in zarr?

Options I considered:

1. Build node somewhere else, then move
   The V2 copy implementations do not seem to be atomic on a quick glance,
   so first building up the group node in a tmp group and then moving it does not resolve the issue.
   I assume this is also highly dependent on the store.

2. Create Locks in zarr store
   Another approach would be the creation of lock files.
   My first idea would be to create temporary groups as lock files.
   Is there a nicer approach for a store-agnostic locking?
   I would like to avoid messing with the lower-level zarr metadata.

Other potential issues?

I guess in all cases I might run into issues with the async approach of v3, or have to force synchronization for the transactions.
Happy to hear any opinions on this.

Thank you and best regards,
Fabricio