You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/10 23:32:18 UTC

[jira] [Commented] (COUCHDB-2938) Filtered changes should use ddoc_cache

    [ https://issues.apache.org/jira/browse/COUCHDB-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141840#comment-15141840 ] 

ASF GitHub Bot commented on COUCHDB-2938:
-----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/couchdb-fabric/pull/37


> 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
>            Assignee: 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)