[couchdb-documentation] branch rfc/004-document-storage updated: Add detail on predicate pushdown

[ko...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

kocolosk pushed a commit to branch rfc/004-document-storage
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git


The following commit(s) were added to refs/heads/rfc/004-document-storage by this push:
     new 85c6368  Add detail on predicate pushdown
85c6368 is described below

commit 85c6368ff3be30ab8447f79d483695b9bd813ac6
Author: Jan Lehnardt <ja...@apache.org>
AuthorDate: Tue Apr 2 10:31:33 2019 -0400

    Add detail on predicate pushdown
    
    Co-Authored-By: kocolosk <ko...@apache.org>
---
 rfcs/004-document-storage.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/rfcs/004-document-storage.md b/rfcs/004-document-storage.md
index 69342ba..3ec406a 100644
--- a/rfcs/004-document-storage.md
+++ b/rfcs/004-document-storage.md
@@ -192,6 +192,8 @@ The disadvantages of this approach are that it uses a larger number of key-value
 pairs and has a higher overall storage overhead from the repeated common key
 prefixes. The new FoundationDB storage engine should eliminate some of the
 storage overhead.
+As per the FoundationDB discussion about being able to co-locate compute operations with data storage servers/nodes](https://forums.foundationdb.org/t/feature-request-predicate-pushdown/954/6), if we were to make use of this hypothetical feature, we’d not get a guarantee of entire documents being co-located on one storage node, requiring us to do extra work should we want to, say, assemble a full `doc` to send to a map function. JS views would have a harder time, while Mango indexes with [...]
+
 
 # Key Changes