couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Dionne (Updated) (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-911) Concurrent updates to the same document generate erroneous conflict messages
Date Fri, 18 Nov 2011 19:10:51 GMT


Bob Dionne updated COUCHDB-911:

    Attachment: 0003-Add-references-to-docs-to-prevent-dups-from-being-co.patch

Thanks Filipe, I ran the test fine and modified the patch to conform to the couchdb style
> Concurrent updates to the same document generate erroneous conflict messages
> ----------------------------------------------------------------------------
>                 Key: COUCHDB-911
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: HTTP Interface
>    Affects Versions: 1.0
>         Environment: Cloudant BigCouch EC2 node
>            Reporter: Jay Nelson
>            Priority: Minor
>             Fix For: 1.2
>         Attachments: 0001-Add-test-test-etap-074-doc-update-conflicts.t.patch, 0001-Add-test-test-etap-074-doc-update-conflicts.t.patch,
0001-Fix-whitespace.patch, 0002-Failing-test-for-duplicates-in-bulk-docs.patch, 0003-Add-references-to-docs-to-prevent-dups-from-being-co.patch
>   Original Estimate: 48h
>  Remaining Estimate: 48h
> Repeating an "_id" in a _bulk_docs post data file results in both entries being reported
as document conflict errors.  The first occurrence actual inserts into the database, and only
the second occurrence should report a conflict.
> curl -d '{ "docs": [ {"_id":"foo"}, {"_id","foo"} ] }' -H 'Content-Type:application/json'
> [{"id":"foo","error":"conflict","reason":"Document update conflict."},{"id":"foo","error":"conflict","reason":"Document
update conflict."}]
> But the database shows that one new document was actually inserted.
> Only the second occurrence should report conflict.  The first occurrence should report
the "_rev" property of the newly inserted doc.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message