[
https://issues.apache.org/jira/browse/COUCHDB-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814945#comment-15814945
]
Robert Newson commented on COUCHDB-3269:
----------------------------------------
maybe not so wrong. the 'offset' field in collector in fabric_view_changes
doesn't mean what I initially thought. Patch is not too far off, but it's still
wrong. We reused the same record as we do in regular views where it _does_ mean
what I thought (the offset of the first row from the beginning of the view).
> 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
>
> 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.4#6332)
