Update Zarr store creation functions#9790
Conversation
|
Can one of the admins verify this patch? Admins can comment |
|
Cool. Happy to see things moved upstream. Is this new functionality widely deployed? Should we be concerned at all about backwards compatibility? (how old is it / what fraction of users are likely using that version or older?) |
|
add to allowlist |
|
CI failure seems unrelated. Testing main here: #9792 |
This should work with all versions of Zarr > 2.6.0, which was released in July, 2021. That feels like a long time ago to me, but I have no data on what fraction of users are using older versions. (Do you have some way to get those numbers?) |
|
Makes sense. I was just curious. CI seems unhappy. I suspect due to unrelated issues. I'm going to pause on this for a moment while I check those out. My apologies for the delay. |
|
Thanks @rabernat . This is in. |
Closes #xxxxpre-commit run --all-filesAs discussed in zarr-developers/zarr-python#1309 (review), Zarr can now handle a the creation of more types of store object from URLs thanks to the FSStore class. This means that usually Dask can just pass through the store URL with no modifications (e.g. calling
get_mapper). The only exception is when the user specifiesstorage_optionsexplicitly.