couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Reopened: (COUCHDB-462) built-in conflicts view
Date Wed, 12 Aug 2009 20:00:14 GMT


Adam Kocoloski reopened COUCHDB-462:

Damien objected to this patch on IRC because it's not performant (it does a full scan over
the by_id btree instead of maintaining a separate index) and because it's not flexible enough
(e.g. no way to identify conflicts from a particular document type).  His suggestion was just
to let users define a custom view if they need aggregate information on conflicts.

I understand and agree with the performance concerns.  I worry that we aren't doing a good
job of helping users develop conflict-aware applications, but we could probably alleviate
that with some extra hand-holding in Futon.

> built-in conflicts view
> -----------------------
>                 Key: COUCHDB-462
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>            Reporter: Adam Kocoloski
>             Fix For: 0.10
>         Attachments: 462-jan-2.patch, conflicts_view.diff, COUCHDB-462-adam-updated.patch,
> This patch adds a built-in _conflicts view indexed by document ID that looks like
> GET /dbname/_conflicts
> {"rows":[
> {"id":"foo", "rev":"1-1aa8851c9bb2777e11ba56e0bf768649", "conflicts":["1-bdc15320c0850d4ee90ff43d1d298d5d"]}
> ]}
> GET /dbname/_conflicts?deleted=true
> {"rows":[
> {"id":"bar", "rev":"5-dd31186f5aa11ebd47eb664fb342f1b1", "conflicts":["5-a0efbb1990c961a078dc5308d03b7044"],
> {"id":"baz", "rev":"2-eec205a9d413992850a6e32678485900", "deleted":true, "deleted_conflicts":["2-10009b36e28478b213e04e71c1e08beb"]}
> ]}
> As the HTTPd and view layers are a bit outside my specialty I figured I should ask for
a Review before Commit.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message