[
https://issues.apache.org/jira/browse/OAK-2926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580359#comment-14580359
]
Chetan Mehrotra commented on OAK-2926:
--------------------------------------
[~tmueller] Should we also support {{resultFetchSize}} like in JR2. This limit
allowed system to validate access to minimum {{resultFetchSize}} before
declaring the size. As per current approach it might be possible for a user to
determine existence of some type of information i.e. more than 0 result size
even if he does not have the access. Having this minimum access check would be
useful
> Fast result size estimate
> -------------------------
>
> Key: OAK-2926
> URL: https://issues.apache.org/jira/browse/OAK-2926
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Labels: performance
> Fix For: 1.3.1, 1.2.3, 1.0.15
>
> Attachments: OAK-2926-b-1.0.patch, OAK-2926-b-1.2.patch,
> OAK-2926-b.patch, OAK-2926-c.patch, OAK-2926.patch
>
>
> When asking for the correct result size of a query, the complete result needs
> to be read, so that access rights checks are made, and (unless the index is
> known to be up-to-date, and can process all conditions) so that the existence
> and all query conditions are checked.
> Jackrabbit 2.x supports a fast way to get an estimate of the result size,
> without doing access rights checks. See also JCR-3858.
> Please note that according to the JCR API, NodeIterator.getSize() may return
> -1 (for "unknown"), and in Oak this is currently done if counting is slow.
> This would also need to be disabled if a fast result size estimate is needed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
