Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Zarr V2 vs V3 #17

Closed
TomNicholas opened this issue Mar 8, 2024 · 3 comments · May be fixed by #182
Closed

Zarr V2 vs V3 #17

TomNicholas opened this issue Mar 8, 2024 · 3 comments · May be fixed by #182
Assignees
@sharkinsspatial
Labels
zarr-python Relevant to zarr-python upstream

Comments

@TomNicholas
Copy link
Member

What needs to be done here?
@TomNicholas TomNicholas added the zarr-python Relevant to zarr-python upstream label Mar 26, 2024
@TomNicholas TomNicholas mentioned this issue Mar 27, 2024
Closed
2 tasks
@TomNicholas
Copy link
Member Author

Ideally we would be able to import Zarr objects from zarr-python that help us navigate the differences between v2 and v3

@TomNicholas
Copy link
Member Author

So Zarr v3 was released last week (it's on PyPI, and can be installed by specifying --pre with pip install). This means we can start the process of refactoring virtualizarr to use the v3 zarr-python library for some internal abstractions.

In particular I want to replace the virtualizarr.zarr.ZArray class. I haven't really looked at the v3 code much at all yet, but I'm hoping there is some drop-in for the ZArray class that can smoothly handle the difference between Zarr v2 and v3 arrays for us. (And if there's not we should be making suggestions upstream.)

@ghidalgo3 ghidalgo3 mentioned this issue Jul 3, 2024
Draft
9 tasks
@ghidalgo3 ghidalgo3 mentioned this issue Jul 10, 2024
Draft
9 tasks
@sharkinsspatial sharkinsspatial self-assigned this Jan 27, 2025
@sharkinsspatial sharkinsspatial mentioned this issue Jan 27, 2025
Open
4 tasks
@maxrjones maxrjones added the v3-migration Required for migration to Zarr-Python 3.0 label Jan 29, 2025
@maxrjones maxrjones removed the v3-migration Required for migration to Zarr-Python 3.0 label Jan 29, 2025
@maxrjones
Copy link
Member

The migration to Zarr-Python 3.0 is being discussed in more detail in #392

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sharkinsspatial sharkinsspatial

Labels
zarr-python Relevant to zarr-python upstream
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add Zarr v3 dependency ghidalgo3/VirtualiZarr
3 participants
@sharkinsspatial @maxrjones @TomNicholas