[
https://issues.apache.org/jira/browse/COUCHDB-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908535#action_12908535
]
Klaus Trainer commented on COUCHDB-885:
---------------------------------------
Note that the procedure I've previously described will create a conflict:
curl -X GET http://127.0.0.1:5984/foobase/doc?conflicts=true
{"_id":"doc","_rev":"3-b06fcd1c1c9e0ec7c480ee8aa467bf3b","foo":"bar","_conflicts":["1-4c6114c65e295552ab1019e2b046b10e"]}
> 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.
