couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vatam...@apache.org
Subject [couchdb-documentation] branch master updated: Update description and examples for _replication_state_time
Date Wed, 19 Apr 2017 02:14:43 GMT
This is an automated email from the ASF dual-hosted git repository.

vatamane pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git

The following commit(s) were added to refs/heads/master by this push:
       new  1cb0e35   Update description and examples for _replication_state_time
1cb0e35 is described below

commit 1cb0e3592727a85acdc5b63cb7e69b309c5ae22f
Author: Jonathan Hall <flimzy@flimzy.com>
AuthorDate: Tue Apr 18 21:05:04 2017 +0200

    Update description and examples for _replication_state_time
---
 src/replication/replicator.rst | 19 +++++++++----------
 1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/src/replication/replicator.rst b/src/replication/replicator.rst
index 1db5c8f..7668ea7 100644
--- a/src/replication/replicator.rst
+++ b/src/replication/replicator.rst
@@ -67,7 +67,7 @@ CouchDB with 3 new fields:
         "create_target":  true,
         "_replication_id":  "c0ebe9256695ff083347cbf95f93e280",
         "_replication_state":  "triggered",
-        "_replication_state_time":  1297974122
+        "_replication_state_time":  "2011-02-17T20:22:02+01:00"
     }
 
 Special fields set by the replicator start with the prefix
@@ -84,9 +84,8 @@ Special fields set by the replicator start with the prefix
 
 - ``_replication_state_time``
 
-  A Unix timestamp (number of seconds since 1 Jan 1970) that tells us
-  when the current replication state (marked in ``_replication_state``)
-  was set.
+  The time in RFC3339 format when the current replication state (marked in
+  ``_replication_state``) was set.
 
 - ``_replication_state_reason``
 
@@ -118,7 +117,7 @@ the document will look like:
         "create_target":  true,
         "_replication_id":  "c0ebe9256695ff083347cbf95f93e280",
         "_replication_state":  "completed",
-        "_replication_state_time":  1297974122
+        "_replication_state_time":  "2011-02-17T20:22:02+01:00"
     }
 
 When an error happens during replication, the ``_replication_state``
@@ -196,7 +195,7 @@ While document ``doc_A`` will look like this:
         "target":  "http://user:pass@localhost:5984/bar",
         "_replication_id":  "c0ebe9256695ff083347cbf95f93e280",
         "_replication_state":  "triggered",
-        "_replication_state_time":  1297974122
+        "_replication_state_time":  "2011-02-17T20:22:02+01:00"
     }
 
 Note that both document get exactly the same value for the ``_replication_id``
@@ -263,7 +262,7 @@ documents which represent pull replications from servers A and B:
         "continuous":  true,
         "_replication_id":  "c0ebe9256695ff083347cbf95f93e280",
         "_replication_state":  "triggered",
-        "_replication_state_time":  1297971311
+        "_replication_state_time":  "2011-02-17T19:35:11+01:00"
     }
 
 .. code-block:: javascript
@@ -275,7 +274,7 @@ documents which represent pull replications from servers A and B:
         "continuous":  true,
         "_replication_id":  "231bb3cf9d48314eaa8d48a9170570d1",
         "_replication_state":  "triggered",
-        "_replication_state_time":  1297974122
+        "_replication_state_time":  "2011-02-17T20:22:02+01:00"
     }
 
 Now without stopping and restarting CouchDB, add another replicator database.
@@ -329,7 +328,7 @@ following pull replication documents in it:
          "continuous":  true,
          "_replication_id":  "c0ebe9256695ff083347cbf95f93e280",
          "_replication_state":  "triggered",
-         "_replication_state_time":  1297971311
+         "_replication_state_time":  "2011-02-17T19:35:11+01:00"
     }
 
 .. code-block:: javascript
@@ -341,7 +340,7 @@ following pull replication documents in it:
          "continuous":  true,
          "_replication_id":  "231bb3cf9d48314eaa8d48a9170570d1",
          "_replication_state":  "triggered",
-         "_replication_state_time":  1297974122
+         "_replication_state_time":  "2011-02-17T20:22:02+01:00"
     }
 
 Now you would like to have the same pull replications going on in server

-- 
To stop receiving notification emails like this one, please contact
['"commits@couchdb.apache.org" <commits@couchdb.apache.org>'].

Mime
View raw message