Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
The replication conficts section of the documentation (http://docs.couchdb.org/en/master/replication/conflicts.html) has not been updated with changes from the 2.0 version, as the recommended procedure still contains use of the all_or_nothing mode, which is no longer supported (if I'm not mistaken… it is no longer documented at http://docs.couchdb.com/en/2.0.0/api/database/bulk-api.html#db-bulk-docs , though not all references to it have been properly cleaned up there, either).
In particular, we would like to know what is the recommended procedure to resolve merges in a post-2.0 world. Confirmation that insertion of conflicting versions can only occur when more than one node is involved would be nice, as well.