-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add new blog post: What's new in Zarr V3 Specification? #60
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think I'd generally reduce some of the high-level prose with a focus on the specific differences.
With the official release around the corner, there's a lot to look forward to. | ||
But before we dive headfirst into integrating Zarr-Python V3 into our workflows, | ||
I want to take a moment to provide an overview of the key changes and enhancements | ||
we've made in this new version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clarify of the spec not the library.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7d3e974.
### Enhanced Interoperability 🔁 | ||
|
||
Zarr V2 was deeply intertwined with the Python ecosystem, particularly relying | ||
on NumPy for many of its core operations. While this made it highly efficient |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe an alternative to "efficient" like customizable or comfortable
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7d3e974.
|
||
### Cloud-Native Performance ☁️ | ||
|
||
Zarr V2 was originally optimized for local file storage, where latency is |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure this is true. Was it not initially for object storage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was. How about something like V2 was designed for local and object storage, but the V2 design was not efficient in handling higher latency per operation in cloud storage?
required. | ||
|
||
Additionally, the structure of the array has been optimized. Chunks are now | ||
grouped into individual directories based on their size, which minimizes the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure I follow this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7d3e974.
types, modify the chunk grid to support irregular chunks, and even add new | ||
codecs. | ||
|
||
One exciting new feature made possible by this extensibility is the [sharding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Except that it's "just a codec", eh?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed in 7d3e974.
Hi all. 👋🏻
Added a new blog post to provide the community with an overview of the V3 specification before we all start enjoying Zarr-Python V3.
Preview: https://zarr-blog--60.org.readthedocs.build/en/60/zarr-v3/
Please review. Thanks!