documentation commit: updated refs/heads/master to 7fcef32

[kx...@apache.org]

Repository: couchdb-documentation
Updated Branches:
  refs/heads/master 18bd16aed -> 7fcef32d2


Document modifying triggered replication documents


Project: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/commit/7fcef32d
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/tree/7fcef32d
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/diff/7fcef32d

Branch: refs/heads/master
Commit: 7fcef32d2cbe5dfa1a9ca1fb265492f0b792578e
Parents: 18bd16a
Author: Mihai Gramada <gr...@gmail.com>
Authored: Thu Jul 23 13:47:23 2015 +0200
Committer: Mihai Gramada <gr...@gmail.com>
Committed: Thu Jul 23 14:36:12 2015 +0200

----------------------------------------------------------------------
 src/replication/replicator.rst | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/couchdb-documentation/blob/7fcef32d/src/replication/replicator.rst
----------------------------------------------------------------------
diff --git a/src/replication/replicator.rst b/src/replication/replicator.rst
index 959bbe6..31ba686 100644
--- a/src/replication/replicator.rst
+++ b/src/replication/replicator.rst
@@ -230,6 +230,23 @@ yet the ``_replication_state`` field set.
     with the value ``triggered``, therefore they're always restarted
     when CouchDB is restarted.
 
+Updating Documents in the Replicator Database
+=============================================
+
+Once the replicator has started work on a job defined in the ``_replicator``
+database, modifying the replication document is no longer allowed. Attempting
+to do this will result in the following response
+
+.. code-block:: javascript
+
+    {
+        "error": "forbidden",
+        "reason": "Only the replicator can edit replication documents that are in the triggered state."
+    }
+
+The way to accomplish this is to first delete the old version and then insert
+the new one.
+
 Changing the Replicator Database
 ================================