You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/04/11 08:24:12 UTC
[jira] [Resolved] (OAK-2753) Use increasing batch size for sorted
queries in LucenePropertyIndex
[ https://issues.apache.org/jira/browse/OAK-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved OAK-2753.
----------------------------------
Resolution: Fixed
Using increasing batch size and also switched to PerfLogger for logging the timings
Done
* trunk - http://svn.apache.org/r1672835
* 1.0 - http://svn.apache.org/r1672838
* 1.2 - http://svn.apache.org/r1672839
> Use increasing batch size for sorted queries in LucenePropertyIndex
> -------------------------------------------------------------------
>
> Key: OAK-2753
> URL: https://issues.apache.org/jira/browse/OAK-2753
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: oak-lucene
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.0.13, 1.3.0, 1.2.1
>
>
> OAK-2133 introduced increasing batch sizes while performing Lucene query. Currently that only happens for unsorted query. Sorted queries still use 50 as batch size.
> This causes slight slowness if the complete cursor is to be read. As a fix use the same approach for sorted queries also
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)