[
https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510673
]
Marcel Reutegger commented on JCR-989:
--------------------------------------
I completely agree with you that both our suggestions are quite ugly ;)
Here's another idea, we could already anticipate what JSR 283 will most
probably specify on the Query interface. See:
https://jsr-283.dev.java.net/issues/show_bug.cgi?id=214
Would that work for you?
> 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
> Priority: Minor
> Attachments: LazyQueryResultImpl.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.
