[
https://issues.apache.org/jira/browse/COUCHDB-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111566#comment-15111566
]
ASF GitHub Bot commented on COUCHDB-2938:
-----------------------------------------
GitHub user chewbranca opened a pull request:
https://github.com/apache/couchdb-fabric/pull/37
Support fetch ddoc logic for filtered changes feeds
This fixes COUCHDB-2938. Companion PR out in
https://github.com/apache/couchdb-couch/pull/134.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/couchdb-fabric
2938-use-ddoc-cache-in-filtered-changes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-fabric/pull/37.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #37
----
commit 8f42a7db69137896efd3c8a44899a9b83f848a10
Author: Russell Branca <[email protected]>
Date: 2016-01-21T22:55:13Z
Support fetch ddoc logic for filtered changes feeds
----
> Filtered changes should use ddoc_cache
> --------------------------------------
>
> Key: COUCHDB-2938
> URL: https://issues.apache.org/jira/browse/COUCHDB-2938
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Russell Branca
>
> One of the primary functions of the ddoc_cache is to avoid having to ship the
> entire ddoc across the wire for every shard. You can see where we do this for
> views in [1]. We currently do not use the same pattern for filtered changes
> feeds, which means we're still susceptible to overloading a network with ddoc
> traffic as the ddoc needs to be sent to every shard that will filter docs. We
> should switch filtered changes feeds to use the same patterns as map and
> reduce views.
> [1]
> https://github.com/apache/couchdb-fabric/blob/master/src/fabric_rpc.erl#L91-L92
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
