[
https://issues.apache.org/jira/browse/COUCHDB-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918927#action_12918927
]
Paul Joseph Davis commented on COUCHDB-911:
-------------------------------------------
You've sent two write commands to the database using a single _rev token. This
means you've got a document that's entered into a conflict. Having the first
occurrence in the results *not* be in conflict would be misleading because it
*is* in conflict.
Theoretically we could add a check to reject _bulk_docs updates with duplicate
_id, _rev pairs, but that doesn't seem like a good idea for some reason.
> Repeating a doc._id in a _bulk_docs request results in erroneous "Document
> conflict" error
> ------------------------------------------------------------------------------------------
>
> Key: COUCHDB-911
> URL: https://issues.apache.org/jira/browse/COUCHDB-911
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 1.0
> Environment: Cloudant BigCouch EC2 node
> Reporter: Jay Nelson
> Priority: Minor
> 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' -X POST
> http://appadvice.cloudant.com/foo/_bulk_docs
> [{"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.
-
You can reply to this email to add a comment to the issue online.
