[
https://issues.apache.org/jira/browse/COUCHDB-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15890504#comment-15890504
]
ASF subversion and git services commented on COUCHDB-3269:
----------------------------------------------------------
Commit 998cf2d66aeb0a436f2d836f3f50ee0c647137fc in couchdb-fabric's branch
refs/heads/2971-count-distinct from [~rnewson]
[ https://git-wip-us.apache.org/repos/asf?p=couchdb-fabric.git;h=998cf2d ]
Handle no_pass message when limit is 0
A view query that uses both a filter and a limit value can appear to
'hang' because the workers continue to run even after the number of
requested items have been returned, as workers that find no more
matches return 'no_pass' messages not 'change' messages, and thus the
short-circuiting code is never activated.
COUCHDB-3269
> view response can 'hang' with filter and limit specified
> --------------------------------------------------------
>
> Key: COUCHDB-3269
> URL: https://issues.apache.org/jira/browse/COUCHDB-3269
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Robert Newson
> Fix For: 2.1.0
>
>
> If you query a large view with both 'filter' and 'limit' specified, couchdb
> will not promptly complete the view response after the requested number of
> rows has been returned.
> This is because view completion happens on receipt of a 'change' or
> 'completed' message from a worker. In the case of a filtered view request,
> the worker might instead return a 'no_pass' message, indicating that no
> documents passed the filter at a given sequence.
> Add a clause in fabric_view_changes to handle this special case and end the
> view response promptly where possible.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
