Alistair Miles

Of course another possible solution to removing old data would be to have some program that is aware of what chunks need to be deleted and deletes them directly from...

On Mon, 5 Nov 2018, 10:57 Jacob Tomlinson For expiring data that was what I was trying to propose. The chunks would > be removed automatically by the underlying storage...

Yes jakirkham's comment captures it nicely. In conceptual terms, an append operation consists of three tasks. First you have to read the array metadata to find out the current shape...

Good point re eventual consistency of object stores. But even if you allow zarr array to have effectively inifinite size dimensions, you still need something somewhere that keeps track of...

Ah sorry, I assumed we were talking about use cases that involve appending, which in my mind means "sticking more data on at the end". Yes I can imagine use...

Thanks @chairmank for this idea, apologies for the delay in responding. This is a neat idea, it is appealing to have symmetry so it is as easy to grow an...

@tam203 that is a beautiful write-up! Knowing this is an important feature for your use cases, I'm more than happy to consider this in scope for the next spec version....

Hi @Carreau, I think it is reasonable if a store does not support deletion. If you agree, then yes I'd suggest we clarify that supporting deletion is optional somehow. E.g.,...

Thanks Benoit. I don't know much about Geospatial data but I'd be very happy to discuss. On Wed, May 18, 2016 at 8:44 AM, Benoit Bovy [email protected] wrote: > Just...

Hi @ianliu, thanks this is very useful to know. Adding a capability for compression into a v3 extension for consolidated metadata sounds like a good idea to me.