[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123017#comment-13123017
]
Adam Kocoloski commented on COUCHDB-1234:
-----------------------------------------
There is no 1.1.2 release of Apache CouchDB. Sounds like a Couchbase thinger
to me.
That being said, I am curious about Filipe's statement that this is resolved in
the replicator in Apache CouchDB 1.1.0. If that's true it seems like we ought
to have backported the fix to 1.0.x.
> "Named Document Replication" does not replicate the "_deleted" revision
> -----------------------------------------------------------------------
>
> Key: COUCHDB-1234
> URL: https://issues.apache.org/jira/browse/COUCHDB-1234
> Project: CouchDB
> Issue Type: Bug
> Components: Replication
> Affects Versions: 1.0.2
> Environment: CentOS 5.5
> Reporter: Hans-D. Böhlau
> Fix For: 1.1
>
>
> I would like to use "Named Document Replication" to replicate changes on a
> number of docs. I expect ALL changes of those docs to be replicated from
> source-db (test1) towards the target-db (test2).
> as-is:
> --------
> If a document changes its revision because of a "normal" modification, it
> works perfectly and fast.
> If a document (hdb1) changes its revision because of its deletion, the
> replicator logs an error. The document in my target-database remains alive.
> couch.log: [error] [<0.6676.3>] Replicator: error accessing doc hdb1 at
> http://vm-dmp-del1:5984/test1/, reason: not_found
> i expected:
> -----------------
> ... "Named Document Replication" to mark a document as deleted in the
> target-db if it has been deleted in the source-db.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
