Please define the delete consistency behaviour

,
1

I have made a small example project to highlight the query I have:

I understand that I can have conditional updates on objects, but what about deleting the objects ? What consistency can I expect to observe ?

If I want consistency of deletions, then should I use a tombstone object to represent a deletion ?

If I use a tombstone, what TTL should I set it to, to ensure that all the caching has definitely caught up and will consistently view it as deleted ?

Given my goals, consistent deletions, is there some other way I am better of using Tigris to accomplish my goals ?

Thank you for making Tigris.

2

@inverted-capital This is something we are actively working on in simplifying and offering this through a single consistency header that can then be used for PUT, GET, LIST, and DELETE operations, offering strong consistency in cases where it is needed. I’m optimistic that we’ll have this ready within a week. To answer your original question, the CAS header that you’re using won’t be sufficient for deletes, which is why we’re streamlining it to just have one header.

3

That’s exciting - thank you. I will use a tombstone in the meantime while I eagerly await your update :star_struck: