Details
-
Bug
-
Resolution: Done
-
Major
-
Mobile 2.1
-
None
Description
Priya has requested some information on the SG/CB tombstone lifecycle management, and it probably would be best described in a doc.
Here's the email, we will answer in comments on this ticket, hopefully with enough information to be spun out into a doc page.
Can you please confirm the behavior of system and also other missing scenarios. Also , can you call out if there are variations depending on SGW versions.
No xattr
----------
- delete through SGW API : remove body + meta
- purge through SGW API : remove body + meta
- delete through SDK : remove body + meta
- purge through SDK : remove body + meta
With XAttr:
--------------
- delete through SGW API : remove body . Preserve meta (in xattr). Tombstone
- purge through SGW API : remove body + meta
- delete through SDK : remove body . Preserve meta (in xattr). Tombstone
- purge through SDK : remove body + meta
TTL on documents in CBS bucket
-------------------------------------
- Confirm that it Purges all documents ? i.e. removes docs + meta
metadata purge on documents :
---------------------------------------
- Rids all meta in xattr . What happens to the doc body ?
Channel Cache cleanup
--------------------
Does this impact if xattr or no xattr.
Assuming the cache cleanup in 2.1.1 + only
Recommended method for users to delete tombstones on server
------------------------------------------------------
- Setting TTL handle it ? Does it matter if its xattr versus no xattr (depends on answer to previous)
- Query for docs with _deleted property is true and then purge them …
- In 5.5, we can do a N1QL query for sync metadata but how do we get the deleted ones from that