In step 7. delete document on the remote database not on the local. Cheers Nikolai
On 12.09.2010, at 20:25, Sebastian Cohnen (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/COUCHDB-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908518#action_12908518 > ] > > Sebastian Cohnen commented on COUCHDB-885: > ------------------------------------------ > > I cannot reproduce. > > 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? > >> Delete document with attachment fails after replication. >> -------------------------------------------------------- >> >> 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 >> >> Step to reproduce the bug: >> 1. Make database "test" on a remote couchdb server that reside on a >> different machine! >> 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. >> >> 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. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >
