You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Hans-D. Böhlau (JIRA)" <ji...@apache.org> on 2011/07/28 15:25:10 UTC
[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
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Jean-Pierre Fiset (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123003#comment-13123003 ]
Jean-Pierre Fiset commented on COUCHDB-1234:
--------------------------------------------
As of 1.1.2, I see the same behaviour as initially reported.
> "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.
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
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Hans-D. Böhlau (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072739#comment-13072739 ]
Hans-D. Böhlau commented on COUCHDB-1234:
-----------------------------------------
Hi *, Randall is right ... thats exactly what I wanted to say: "Replication by id will not replicate a delete".
> "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] [Closed] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Filipe Manana (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filipe Manana closed COUCHDB-1234.
----------------------------------
Resolution: Fixed
Fix Version/s: 1.1
> "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
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
[ 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] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Filipe Manana (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Randall Leeds (JIRA)" <ji...@apache.org>.
[ 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-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Filipe Manana (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123016#comment-13123016 ]
Filipe Manana commented on COUCHDB-1234:
----------------------------------------
Jean-Pierre, I think you're talking about Couchbase 1.1.2, which is based in Apache CouchDB 1.0.x.
This issue doesn't exist anymore as of Apache CouchDB 1.1.0. My understanding is that Couchbase is releasing a version vased on Apache CouchDB 1.1.x soon.
> "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
[jira] [Commented] (COUCHDB-1234) "Named Document Replication" does
not replicate the "_deleted" revision
Posted by "Adam Kocoloski (Commented) (JIRA)" <ji...@apache.org>.
[ 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