draft blog post #21
draft blog post #21
Conversation
| intermediary groups. | ||
|
|
||
| - Zarr V3 has an explicit root, while v2 roots and groups could not be | ||
| distinguished. This mean that you can only open a zarr v3 at a specific |
There was a problem hiding this comment.
This was one of the first things that readers commented on to me. I wonder if the implementation details could discuss walking up the implicit hierarchy to detect the root a la git?
There was a problem hiding this comment.
I've clarified; having a single root is a spec difference, automatically finding the root is an implementation and user convenience. The core function can perfectly refuse to open a non-root, but the user exposed one can do all the magic they want.
In the same way that right now a store can be just a string that start with s3:// and will converted to an actual Store()
Co-authored-by: Josh Moore <j.a.moore@dundee.ac.uk>
|
@MSanKeys963 : thoughts on resurrecting this? |
I can see using some parts of this draft for my next blog post on Zarr v3 spec. |
|
Whatever works best. |
No description provided.