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.

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

Blosc2 #21

Open
mkitti opened this issue May 18, 2023 · 4 comments
Open

Blosc2 #21

mkitti opened this issue May 18, 2023 · 4 comments
Labels
enhancement New feature or request

Comments

@mkitti
Copy link

mkitti commented May 18, 2023

I see that you are primarily using c-blosc 1. Have you considered c-blosc 2? It is being much more actively developed than c-blosc 1 and corrects some significant deficiencies.
https://github.com/Blosc/c-blosc2

We'll probably need zarr-developers/numcodecs#413 , but this is overdue.

@aliddell
Copy link
Member

We had started out with C-Blosc 2 but quickly ran into exactly what you noted: zarr-python (actually numcodecs) couldn't read what we wrote, which is a non-starter. We're definitely interested in upgrading and we're following that issue.

@mkitti
Copy link
Author

mkitti commented May 18, 2023

I just got c-blosc 1 to address a known corruption issue in ZSTD, so please use c-blosc version 1.21.4 or greater to avoid that.
Blosc/c-blosc#364

@joshmoore
Copy link

I'll add that in general there's also the consideration of whether or not the generated data can be accessed beyond zarr-python.

With Zarr v3, that will be covered by the individual ZEPs covering different codecs.

@mkitti
Copy link
Author

mkitti commented Sep 20, 2023

A Blosc 2 PR is now pending as developed at the NumFocus Summit: zarr-developers/numcodecs#463

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

3 participants