[
https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519626
]
Christoph Kiehl commented on JCR-989:
-------------------------------------
Okay. What to do now? Based on the discussion on the dev list
(http://www.nabble.com/JCR-2.0-extensions-tf4235046.html#a12049594) it seems
like everyone agrees that we should start to make the jsr283 api available in
Jackrabbit (e.g. in the org.apache.jackrabbit.jsr283 package). Should I remove
the JackrabbitQuery interface? But I think we should the push the effort make
the jsr283 api availble.
> Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically
> ------------------------------------------------------------------------------
>
> Key: JCR-989
> URL: https://issues.apache.org/jira/browse/JCR-989
> Project: Jackrabbit
> Issue Type: New Feature
> Components: query
> Affects Versions: 1.3
> Reporter: Christoph Kiehl
> Assignee: Christoph Kiehl
> Priority: Minor
> Fix For: 1.4
>
> Attachments: jackrabbit-api.patch, jackrabbit-core.patch
>
>
> In our application we have a search which only shows part of a query result.
> We always know which part of the result needs to be shown. This means we know
> in advance how many results need to be fetched. I would like to be able to
> programmatically set resultFetchSize to minimize the number of loaded lucene
> docs and therefore improve the performance.
> I know it is already possible to the set the resultFetchSize via the index
> configuration, but this number is fixed and doesn't work well in environments
> where you use paging for your results because if you set this number too low
> the query will be executed multiple times and if you set it too high too many
> lucene docs are loaded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
