couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan Vander Wilt (JIRA)" <j...@apache.org>
Subject [jira] [Created] (COUCHDB-1950) ddoc-based conflict resolution
Date Tue, 03 Dec 2013 00:28:35 GMT
Nathan Vander Wilt created COUCHDB-1950:
-------------------------------------------

             Summary: ddoc-based conflict resolution
                 Key: COUCHDB-1950
                 URL: https://issues.apache.org/jira/browse/COUCHDB-1950
             Project: CouchDB
          Issue Type: Improvement
            Reporter: Nathan Vander Wilt


This was discussed at CouchConf in Vancouver last month, but didn't see a hook here I could
refer to in another conversation, so…

It'd be great if a design document could include a conflict resolver function, in the vein
of other "app logic" handler hooks like validate_doc_write. I imagine it would look something
like either "function (currentWinner, nextWinningestLoser, parent)" (simply called multiple
times if more than 2 leafs) or simply "function (arrayOfDocs, revisionHistor)" — if it returns
a document, that's the winner, if not the next design document in line gets a pass at it.
(Bonus: if it throws, the conflict stays no matter what other resolvers say?)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message