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 n.teofilov@gmail.com
 designates 209.85.161.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=NuKTU0yhE8ssCFI5GPKjVIH4NqZrU2OVN2k6i/SxZ+XPLsnx/BzM+EixOFeEArGzyS
         J/o3shCBum4YbcpAmT+04ZWbugqvF2P/K4Tf2ArWYaCi4RfawSMXSR/iTfM9MlOpzFSC
         B/xnTCXVxJ6LaH71dh+g4q8tOyP3ZisKj+RV4=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: [jira] Commented: (COUCHDB-885) Delete document with attachment
 fails after replication.
From: Nikolai Teofilov <n.teofilov@gmail.com>
In-Reply-To: <1DA4AB83-E69F-4C0E-8C26-BE5CF446B56E@googlemail.com>
Date: Sun, 12 Sep 2010 21:17:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BE5EDD3-41F4-4085-8A52-7D42E826069A@gmail.com>
References: <13836055.142391284315933097.JavaMail.jira@thor>
 <84F586EF-E228-412C-B3A8-DA092CCEC220@gmail.com>
 <1DA4AB83-E69F-4C0E-8C26-BE5CF446B56E@googlemail.com>
To: dev@couchdb.apache.org

Hi Sebastian!

If you try now the same sequence on two databases residing on a one =
server there is no such a problem so i think this is a replication bug =
that introduce a conflict like Klaus said, but there shouldn't be a =
conflict.

Cheers,
Nikolai

=20
On 12.09.2010, at 21:05, Sebastian Cohnen wrote:

> I've updated the script and can confirm the issue.
>=20
> On 12.09.2010, at 20:47, Nikolai Teofilov wrote:
>=20
>> In step 7. delete document on the remote database not on the local.
>>=20
>> Cheers
>> Nikolai
>>=20
>> On 12.09.2010, at 20:25, Sebastian Cohnen (JIRA) wrote:
>>=20
>>>=20
>>>  [ =
https://issues.apache.org/jira/browse/COUCHDB-885?page=3Dcom.atlassian.jir=
a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1290851=
8#action_12908518 ]=20
>>>=20
>>> Sebastian Cohnen commented on COUCHDB-885:
>>> ------------------------------------------
>>>=20
>>> I cannot reproduce.
>>>=20
>>> But I'm not sure if I understand your steps correctly, so I've =
written a bash script (see =
http://www.friendpaste.com/6SrHCU1lseUURuwTJEpCpk) to execute your =
steps. Could you have a look and verify that I understood your steps =
correctly?
>>>=20
>>>> Delete document with attachment fails after replication.
>>>> --------------------------------------------------------
>>>>=20
>>>>              Key: COUCHDB-885
>>>>              URL: https://issues.apache.org/jira/browse/COUCHDB-885
>>>>          Project: CouchDB
>>>>       Issue Type: Bug
>>>>       Components: Replication
>>>> Affects Versions: 1.0.1
>>>>      Environment: Mac OSX, Windows XP, Windows 7
>>>>         Reporter: Nikolai Teofilov
>>>>=20
>>>> Step to reproduce the bug:
>>>> 1.  Make database "test" on a remote couchdb server that reside on =
a different machine!=20
>>>> 2.  Create new document:  "http://remote-server:5984/test/doc"
>>>> 3.  Create database "test"  on the local couchdb  server.
>>>> 4.  Trigger pull replication  http://remote-server:5984/test -> =
http://localhost:5984/test
>>>> 5.  Attach a file to the replicated document on the local couchdb =
server.
>>>> 6.  Trigger push replication http://localhost:5984/test  -> =
http://remote-server:5984/test
>>>> 7.  Delete the replicated document that contain now the attachment =
on remote database.
>>>>=20
>>>>    This operation will delete the last revision of the document =
(after the replication) but the previous revision of the document =
(before the replication) still exist in the database.
>>>> This defect appears only for replications between databases on two =
different couchdb servers, and only for documents that were updated with =
a new attachment.
>>>=20
>>> --=20
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>=20
>>=20
>=20