You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by Apache Wiki <wi...@apache.org> on 2013/04/12 20:36:10 UTC
[Couchdb Wiki] Update of "Replication" by RobertNewson
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Couchdb Wiki" for change notification.
The "Replication" page has been changed by RobertNewson:
http://wiki.apache.org/couchdb/Replication?action=diff&rev1=53&rev2=54
Comment:
_replicator is a complementary feature, not a replacement for _replicate
Changes on the master will not automatically replicate to the slaves. See “Continuous Replication” below.
- === Run Replication, using the old API ===
+ === One-shot Replication ===
+ One-shot replication is triggered by sending a POST request to the `_replicate` URL.
-
- '''NOTE:''' Before CouchDB 1.1, replication was triggered by sending a POST request to the `_replicate` URL. Many of the concepts and parameters are similar, but '''you are encouraged to use the [[#Replicator_database|replicator database]] instead''' of the old API documented here.
The body is JSON with the following allowed fields:
@@ -75, +74 @@
=== Continuous replication ===
+
To make replication continuous, add "continuous":true parameter to JSON, for example:
{{{
@@ -216, +216 @@
== Replicator database ==
- Since CouchDB 1.1.0, a system database named `_replicator` can be used to manage replications. Replications triggered by POSTing to /_replicate/ (the old API) are not managed by this system database.
+ Since CouchDB 1.1.0, a system database named `_replicator` can be used to manage replications. Replications triggered by POSTing to /_replicate are not managed by this system database.
The currently most reliable documentation about it can be found at:
https://gist.github.com/832610 (from the author)