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

[v3] It is possible to create v3 data with features not currently written into the spec (dtypes, codecs, etc.) #2411

Closed
Tracked by #2412
jhamman opened this issue Oct 18, 2024 · 1 comment · Fixed by #2556
Assignees
Labels
bug Potential issues with the zarr-python library
Milestone

Comments

@jhamman
Copy link
Member

jhamman commented Oct 18, 2024

Zarr version

3.0.0.beta

Numcodecs version

0.13

Python Version

3.11

Operating System

Mac

Installation

pip

Description

We have discussed adding a warning when writing data to zarr_format=3 that is outside the current spec. Currently, this mostly applies to data types and codecs but also includes stores (e.g. ZipStore).

@jhamman jhamman added the bug Potential issues with the zarr-python library label Oct 18, 2024
@jhamman jhamman added this to the 3.0.0 milestone Oct 18, 2024
@jhamman jhamman moved this to Todo in Zarr-Python - 3.0 Oct 18, 2024
@jhamman jhamman added the V3 label Oct 18, 2024
@normanrz
Copy link
Member

normanrz commented Dec 6, 2024

Things we need to put warnings on

  • variable length string/bytes codecs and dtype
  • consolidated metadata

numcodecs codecs already report a warning

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Potential issues with the zarr-python library
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants