[
https://issues.apache.org/jira/browse/OAK-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661659#comment-14661659
]
Thomas Mueller commented on OAK-2977:
-------------------------------------
> Strange is that I found an additional problem with getSize for "order by"
> queries
I found out what the problem was: the test cases now run with fastResultSize
enabled (except when explicitly disabled), so that the timeout was set to 0.
This made the prefetch size smaller (20 instead of 100), which triggered the
problem. So, without the patch, the size was still -1 even if fastResultSize
enabled and "order by" is used, and with the patch, such queries return the
right size.
> Fast result size estimate: OSGi configuration
> ---------------------------------------------
>
> Key: OAK-2977
> URL: https://issues.apache.org/jira/browse/OAK-2977
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Labels: doc-impacting
> Fix For: 1.3.5
>
> Attachments: OAK-2977.patch
>
>
> The fast result size option in OAK-2926 should be configurable, for example
> over OSGi.
> The resultFetchSize should be configurable as well. Currently it is hardcoded
> (PREFETCH_MAX = 100).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
