[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13081155#comment-13081155
]
Filipe Manana commented on COUCHDB-1234:
----------------------------------------
Ok, i was thinking that by "named document replication" you were talking about
the replicator database (1.1), but this doesn't apply since it's version 1.0.2.
You're issue should no longer happen in 1.1.0.
> "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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
