Return-Path: X-Original-To: apmail-couchdb-dev-archive@www.apache.org Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5B30210AA3 for ; Mon, 9 Dec 2013 13:44:14 +0000 (UTC) Received: (qmail 41901 invoked by uid 500); 9 Dec 2013 13:44:12 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 41752 invoked by uid 500); 9 Dec 2013 13:44:10 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 41703 invoked by uid 99); 9 Dec 2013 13:44:08 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Dec 2013 13:44:08 +0000 Date: Mon, 9 Dec 2013 13:44:08 +0000 (UTC) From: "Robert Newson (JIRA)" To: dev@couchdb.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/COUCHDB-1950?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13= 843150#comment-13843150 ]=20 Robert Newson commented on COUCHDB-1950: ---------------------------------------- This is confusing. You're asking me to elaborate on the thing I said we sho= uld not do at all (actually resolve conflicts). On another ticket, one about the read-time ddoc-mediate choice of 'winning'= leaf, I would elaborate a bit more (though it seems pretty straightforward= ). > 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)