-
-
Notifications
You must be signed in to change notification settings - Fork 364
Open
Labels
bugPotential issues with the zarr-python libraryPotential issues with the zarr-python library
Description
Zarr version
3.0.6
Numcodecs version
0.15.1
Python Version
3.13
Operating System
Mac
Installation
using uv to install in virtual environment
Description
We could initialize cached fsspec instances in Zarr v2 by passing protocol and storage options. This doesn't work in v3 anymore even though the cache gets initialized.
Steps to reproduce
import zarr
remote_store = "gs://<bucket>/<prefix>" # example remote store
root = zarr.open_consolidated(f"simplecache::{remote_store}", storage_options={"simplecache": {"cache_storage": "./test_cache"}})
%time _ = root["array"][3600, 2048:4096] # example read
- This gives store not being initialized with async warning
- The cache directory gets created as expected
fs
property ofroot.store
shows the correct Cached fsspec instance- Once reads are done, it always fetches from remote and doesn't use cache.
As I mentioned before, this works fine on v2.
NickGeneva
Metadata
Metadata
Assignees
Labels
bugPotential issues with the zarr-python libraryPotential issues with the zarr-python library