Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of matt.goodall@gmail.com
 designates 209.85.128.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=SmUX5GxQgX7LrQ13r5OyuTKWJyi8p6hJ1VPpRlSsoYrcrZJ+XY8sQjK8bfe/2GjLh/
         tGvRynxwLzxVF6DPzrv6BpaCvvOC2F4eb2U4gJDklFg1G9uMFEYSIZD3tPevIWbv50YC
         5bhUM6JM88sWlxOrqDX7J5MinC+1SFip/xrT8=
MIME-Version: 1.0
In-Reply-To: <1879902179.1232801519966.JavaMail.jira@brutus>
References: <450773094.1230742912301.JavaMail.jira@brutus>
	 <1879902179.1232801519966.JavaMail.jira@brutus>
Date: Sat, 24 Jan 2009 20:29:08 +0000
Message-ID: <214c385b0901241229n5376edf2p64a964ce27264246@mail.gmail.com>
Subject: Re: [jira] Closed: (COUCHDB-188) _bulk_docs fails when deleting and
	adding a doc with the same id
From: Matt Goodall <matt.goodall@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

I'm a bit confused why this was closed. Perhaps a description of the
"new behaviour" is available somewhere?

The only mention of anything related to a change in _bulk_docs I've
*noticed* is about not failing everything in the list of updates
(might be nice if that was optional, actually) and the associated
error reporting. However, that doesn't necessarily fix the problem I
described.

Can anyone explain how the planned change fixes things?

Thanks, Matt

2009/1/24 Jan Lehnardt (JIRA) <jira@apache.org>:
>
>     [ https://issues.apache.org/jira/browse/COUCHDB-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jan Lehnardt closed COUCHDB-188.
> --------------------------------
>
>       Resolution: Invalid
>    Fix Version/s: 0.9
>
> bulk update will get a new behaviour in 0.9. Closing
>
>> _bulk_docs fails when deleting and adding a doc with the same id
>> ----------------------------------------------------------------
>>
>>                 Key: COUCHDB-188
>>                 URL: https://issues.apache.org/jira/browse/COUCHDB-188
>>             Project: CouchDB
>>          Issue Type: Bug
>>          Components: Database Core
>>    Affects Versions: 0.9
>>         Environment: CouchDB revision 730414.
>>            Reporter: Matt Goodall
>>             Fix For: 0.9
>>
>>
>> CouchDB returns a "412 Precondition Failed" when the list of changes sent to _bulk_docs deletes a document and later creates a document with the same id as the deleted document:
>>     {"docs": [
>>         {"_id": "docid", "_rev": "<rev>", "_deleted": true},
>>         {"_id": "docid"}
>>         ]}
>> Once fixed, the response JSON document  will return the same docid twice in the list but it's presumably ordered consistently with the request data so any client should be able to understand the response.
>> Demonstrating the problem using curl is easy enough:
>> $ curl -X PUT http://localhost:5984/test
>> {"ok":true}
>> $ curl -X PUT -d "{}" http://localhost:5984/test/docid
>> {"ok":true,"id":"docid","rev":"4140747751"}
>> $ curl -X POST -d '{"docs": [{"_id": "docid", "_rev": "4140747751", "_deleted": true}, {"_id": "docid"}]}' http://localhost:5984/test/_bulk_docs
>> {"error":"conflict","reason":"Document update conflict."}
>> Note: this is likely related to COUCHDB-172.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>