Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
0.3
-
None
-
Unknown
-
Description
REPLICAT-19 was fixed, but there is one thing left: when a document is restored in one instance it's properly restored in other instances too except that the restored batch stay there, so if you delete the document again the other instance will have two versions of the deleted document.
The first problem is how to identify a deleted document to remove, since it's not going to have the same id in the source and in the target instance.
Then there is 2 possibilities:
1) skip the document change event in case of restore and replicate the restoration of a document instead (which should not be a big problem since we share the batch id)
2) restore each document separately as a complete update and react to the delete of a trash bin element
1) is much faster in terms of communication (just replicate an id) but some things might go wrong during the restoration of a batch on one instance and not in the others (the deleted document not existing anymore on the target instance for some reason).
Attachments
Issue Links
- depends on
-
XWIKI-18945 Produce events around the restoration of a deleted document
- Closed