You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This also fails for mode="a" or mode="a+", but works on mode="w". Unfortunately, I cannot use mode="w" as I do not wish to truncate the file, but rather re-open an existing Zarr array for modification. On testing, it appears that mode="w" does not actually truncate the .zarr directory, which I believe conflicts with julia's definition for open modes / is inconsistent with python Zarr.
Much appreciate your efforts to bring Zarr to Julia!
The text was updated successfully, but these errors were encountered:
Sorry for this, this is definitely bad documentation/implementation. Mode "w" does not truncate but is actually equivalent to "a". When originally implementing this I was following the mental model of NetCDF modes and only made a difference between Read-only and Read/Write modes and just called them "r" and "w" without thinking a lot.
Yes, we should fix this, but this will be breaking in a very nasty way, when silently changing the behavior of "w" to actually truncate the file while in the past it meant "append". So I would suggest to have a full deprecation cycle on this... Will think about it a bit, but please suggest solutions in case you have ideas.
This fails:
This also fails for
mode="a"
ormode="a+"
, but works onmode="w"
. Unfortunately, I cannot usemode="w"
as I do not wish to truncate the file, but rather re-open an existing Zarr array for modification. On testing, it appears thatmode="w"
does not actually truncate the.zarr
directory, which I believe conflicts with julia's definition for open modes / is inconsistent with python Zarr.Much appreciate your efforts to bring Zarr to Julia!
The text was updated successfully, but these errors were encountered: