couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
Date Mon, 09 Dec 2013 13:32:09 GMT


Robert Newson commented on COUCHDB-1950:

Allowing programmatic control over which leaf is returning by GET /dbname/docid is much less
controversial than "ddoc-based conflict resolution", since that brings the real danger of
destroying eventual consistency and creating positive edit cycle feedback. I'd support the
former, but not the latter.

> ddoc-based conflict resolution
> ------------------------------
>                 Key: COUCHDB-1950
>                 URL:
>             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

View raw message