[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does not replicate the "_deleted" revision
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072567#comment-13072567 ] Randall Leeds commented on COUCHDB-1234: A regular replication will replicate the delete. I think OP is saying that replication by id will not replicate a delete, but instead throw an error. Seems like a bug to me. > "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
[jira] [Commented] (COUCHDB-1235) _changes?feed=continuous&descending=true is stupid
[ https://issues.apache.org/jira/browse/COUCHDB-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072566#comment-13072566 ] Randall Leeds commented on COUCHDB-1235: +1. Just commit it. > _changes?feed=continuous&descending=true is stupid > -- > > Key: COUCHDB-1235 > URL: https://issues.apache.org/jira/browse/COUCHDB-1235 > Project: CouchDB > Issue Type: Bug >Reporter: Robert Newson > > Disallow descending=true for continuous changes feed. You don't get updates > past the seq of the db when you started. > Either ignore or throw a 400. Preference for a 400. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (COUCHDB-1235) _changes?feed=continuous&descending=true is stupid
_changes?feed=continuous&descending=true is stupid -- Key: COUCHDB-1235 URL: https://issues.apache.org/jira/browse/COUCHDB-1235 Project: CouchDB Issue Type: Bug Reporter: Robert Newson Disallow descending=true for continuous changes feed. You don't get updates past the seq of the db when you started. Either ignore or throw a 400. Preference for a 400. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does not replicate the "_deleted" revision
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072415#comment-13072415 ] Filipe Manana commented on COUCHDB-1234: And if you don't trigger a "named document replication", doesn't the same happens? > "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
[jira] [Created] (COUCHDB-1234) "Named Document Replication" does not replicate the "_deleted" revision
"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
