You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@couchdb.apache.org by "Pierre Lebeaupin (JIRA)" <ji...@apache.org> on 2017/04/07 11:03:41 UTC

[jira] [Created] (COUCHDB-3366) Replication Conflicts doc section is not up to date with 2.0 changes

Pierre Lebeaupin created COUCHDB-3366:
-----------------------------------------

             Summary: Replication Conflicts doc section is not up to date with 2.0 changes
                 Key: COUCHDB-3366
                 URL: https://issues.apache.org/jira/browse/COUCHDB-3366
             Project: CouchDB
          Issue Type: Bug
          Components: Documentation
            Reporter: Pierre Lebeaupin


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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)