Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Mon, 9 Dec 2013 13:52:09 +0000 (UTC)
From: "Jan Lehnardt (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12682276.1386030425314.2365.1386597129438@arcas>
In-Reply-To: <JIRA.12682276.1386030425314@arcas>
References: <JIRA.12682276.1386030425314@arcas>
Subject: [jira] [Commented] (COUCHDB-1950) ddoc-based conflict resolution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COUCHDB-1950?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
843159#comment-13843159 ]=20

Jan Lehnardt commented on COUCHDB-1950:
---------------------------------------

(sorry if that was confusing)

> 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=E2=80=A6
> It'd be great if a design document could include a conflict resolver func=
tion, in the vein of other "app logic" handler hooks like validate_doc_writ=
e. 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)" =E2=80=94 if it r=
eturns a document, that's the winner, if not the next design document in li=
ne gets a pass at it. (Bonus: if it throws, the conflict stays no matter wh=
at other resolvers say?)


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)