-
-
Notifications
You must be signed in to change notification settings - Fork 331
Remove/relax erroneous "meta" path check #1123
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
Conversation
this avoids disallowing key names such as 'metabolite', for instance
@joshmoore, this seems relatively high priority to get in for v2.13 as it was a regression in behavior for Zarr v2 arrays introduced in 2.12. |
Codecov Report
@@ Coverage Diff @@
## main #1123 +/- ##
=======================================
Coverage 99.94% 99.94%
=======================================
Files 35 35
Lines 13965 13967 +2
=======================================
+ Hits 13958 13960 +2
Misses 7 7
|
I will try this version on our files later today or tomorrow and let you know. |
@grlee77 it is working on our datasets that have a "metadata" group now 👍🏻 |
Thanks, @tasansal. I've added a test (that fails without this PR) and will get this into a pre-release this morning. I'll follow up with 2.13.0 ASAP. |
Oddly, the test I added here is failing on conda-forge: conda-forge/zarr-feedstock#65 cc: @jakirkham |
[Description of PR]
resolves #1105
This PR removes the check disallowing keys starting with "meta" from the Zarr v2 code path. It was not there previously and appears to have been accidentally introduced along with the preliminary v3 support.
For v3, the check is updated to disallow starting with "meta/" instead of "meta" for consistency with
StoreV3._validate_key
(used by the__setitem__
method of various v3 store classes).TODO:
* [ ] Add docstrings and API docs for any new/modified user-facing classes and functions* [ ] New/modified features documented in docs/tutorial.rst