Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of koeglstefan@gmail.com
 designates 209.85.210.180 as permitted sender)
Received-SPF: pass (google.com: domain of koeglstefan@gmail.com designates
 10.50.181.169 as permitted sender) client-ip=10.50.181.169;
MIME-Version: 1.0
In-Reply-To: <86FAED34-1BA3-4641-ACFB-FEEAC063C412@apache.org>
References: 
 <CAPinO9cf5a40pLDtXfcistcXR6aTv-0_xtcqjOJ=o3EV9KmSZQ@mail.gmail.com>
	<86FAED34-1BA3-4641-ACFB-FEEAC063C412@apache.org>
Date: Fri, 2 Mar 2012 14:11:03 +0100
Message-ID: 
 <CAPinO9eZ-2FWfgPiLfjxHj6j0Rum9Cbbv1JwSjp+fRDb_zHwhg@mail.gmail.com>
Subject: Re: Update Conflict for PUT/DELETE in _replicator
From: =?ISO-8859-1?Q?Stefan_K=F6gl?= <koeglstefan@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 2, 2012 at 1:39 PM, Jan Lehnardt <jan@apache.org> wrote:
> On Mar 2, 2012, at 13:25 , Stefan K=F6gl wrote:
>> Again something I noticed during my 1.2.x experiments: It seems I
>> can't update or remove a document from the _replicator database, which
>> I use for pull-replication into my 1.2.x instance.
>>
>> # get current _rev
>> $ curl http://127.0.0.1:5984/_replicator/mygpo
>> {"_id":"mygpo","_rev":"131-57b4da8d3163468cb0bbf4fd30c87832","source":"*=
***********************","target":"http://127.0.0.1:5984/mygpo","create_tar=
get":false,"continuous":true,"user_ctx":{"name":"stefan","roles":["admin"]}=
,"owner":"stefan","_replication_state":"triggered","_replication_state_time=
":"2012-03-02T02:56:12+00:00","_replication_id":"f9fc5457b278d3cdb1ba2f1881=
253b04"}
>>
>> # try to delete
>> $ curl -X DELETE
>> "http://127.0.0.1:5984/_replicator/mygpo?_rev=3D131-57b4da8d3163468cb0bb=
f4fd30c87832"
>> {"error":"conflict","reason":"Document update conflict."}
>
> this should be ?rev=3D... (no underscore)

Of course, I also tried that but it didn't work either... see below.


>> $ curl -X PUT "http://127.0.0.1:5984/_replicator/mygpo" -d @replication.=
json
>
> Can you try adding the ?rev=3D in the URL as well?

# get the rev first
$ curl http://127.0.0.1:5984/_replicator/mygpo
{"_id":"mygpo","_rev":"131-57b4da8d3163468cb0bbf4fd30c87832","source":"****=
****************","target":"http://127.0.0.1:5984/mygpo","create_target":fa=
lse,"continuous":true,"user_ctx":{"name":"stefan","roles":["admin"]},"owner=
":"stefan","_replication_state":"triggered","_replication_state_time":"2012=
-03-02T02:56:12+00:00","_replication_id":"f9fc5457b278d3cdb1ba2f1881253b04"=
}

# delete with rev instead of _rev
$ curl -X DELETE
"http://127.0.0.1:5984/_replicator/mygpo?rev=3D131-57b4da8d3163468cb0bbf4fd=
30c87832"
{"error":"conflict","reason":"Document update conflict."}

# now PUT with rev in URL
$ curl -X PUT "http://127.0.0.1:5984/_replicator/mygpo?rev=3D131-57b4da8d31=
63468cb0bbf4fd30c87832"
-d @replication.json
{"error":"conflict","reason":"Document update conflict."}

# still the same rev (no other change in between)
$ curl http://127.0.0.1:5984/_replicator/mygpo
{"_id":"mygpo","_rev":"131-57b4da8d3163468cb0bbf4fd30c87832","source":"****=
****************","target":"http://127.0.0.1:5984/mygpo","create_target":fa=
lse,"continuous":true,"user_ctx":{"name":"stefan","roles":["admin"]},"owner=
":"stefan","_replication_state":"triggered","_replication_state_time":"2012=
-03-02T02:56:12+00:00","_replication_id":"f9fc5457b278d3cdb1ba2f1881253b04"=
}


-- Stefan