concurrentOpRestores option in Tombstone collections
mweidner037 opened this issue · comments
Undoing the deletions here: 50ba8a1
I've turned this off because I'm not sure it's always correct. Ancestors interfering with messages might make it so that different replicas see different sets of Change events, and then their keySets would not be consistent.
May be easier now that we can intercept send calls from children.
While this is possible in principle, I'll leave it to apps to do this themselves: whenever they perform a Collab operation that should un-archive its value, they can call "restore" on the containing collection.