couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [couchdb-documentation] branch master updated: Document deletion approach when using filtered replication
Date Sun, 19 Mar 2017 22:43:28 GMT
This is an automated email from the ASF dual-hosted git repository.

wohali pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
       new  67139cc   Document deletion approach when using filtered replication
67139cc is described below

commit 67139cc96d4bffdd10d3e2cab02a86e569b220a2
Author: Joan Touzet <>
AuthorDate: Sun Mar 19 18:41:32 2017 -0400

    Document deletion approach when using filtered replication
    Addresses PR #92 and COUCHDB-1893.
 src/replication/intro.rst | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/replication/intro.rst b/src/replication/intro.rst
index 1a3f08d..8890af4 100644
--- a/src/replication/intro.rst
+++ b/src/replication/intro.rst
@@ -95,6 +95,17 @@ only replicated if the filter returns `true`.
     Using a selector provides performance benefits when compared with using a
     :ref:`filterfun`. You should use :ref:`selectorobj` where possible.
+.. note::
+    When using replication filters that depend on the document's content,
+    deleted documents may pose a problem, since the document passed to the
+    filter will not contain any of the document's content. This can be
+    resolved by adding a ``_deleted:true`` field to the document instead
+    of using the DELETE HTTP method, paired with the use of a
+    :ref:`validate document update <vdufun>` handler to ensure the fields
+    required for replication filters are always present. Take note, though,
+    that the deleted document will still contain all of its data (including
+    attachments)!
 Migrating Data to Clients

To stop receiving notification emails like this one, please contact
['"" <>'].

View raw message