jakirkham

> Especially when you couple it with an object store like S3 which uses eventual consistency which would result in you never quite knowing if your update has taken place...

It’d be interesting to hear if anyone has thoughts on a good way to implement an immutable store interface for Zarr. From our discussion it sounds like that gets at...

This has some similarities with the proposal in issue ( https://github.com/zarr-developers/zarr-specs/issues/82 )

Think what Matthias was referring to is `ZipStore` allows writing, but not deletion. So the `erase*` functions don't work. Similarly writing behaves more like write-once (since deletion is not supported)....

Sounds good. Was waiting until we resolved the naming and licensing issues.

Also related ( https://github.com/zarr-developers/zarr-specs/issues/81 ) Somewhat related more general Zarr Python discussion ( https://github.com/zarr-developers/zarr-python/issues/216 )

Here's [the current code in Zarr Python]( https://github.com/zarr-developers/zarr-python/blob/fd979fbda3cf52dc79c3b1e49a8da0a75b03078d/zarr/meta.py#L230-L235 ) for handling these values. One thought might be to graduate this to inclusion in the spec as-is. Idk if there are...

Being able to parse with normal JSON libraries makes sense. Well the type information of the `fill_value` should match the `data_type` of the array, right? Or is the concern the...

Ah sorry thought from our conversation earlier this was `fill_value` focused. That being said, the issue is more or less the same in either case. We are storing values in...

Also issue ( https://github.com/zarr-developers/zarr-specs/issues/82 )