jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-989) Modify LazyQueryResultImpl to allow resultFetchSize to be set programmatically
Date Wed, 08 Aug 2007 07:05:05 GMT

    [ https://issues.apache.org/jira/browse/JCR-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518354
] 

Jukka Zitting commented on JCR-989:
-----------------------------------

Nice work!

I'm not 100% sure if we should place JCR 2.0 extensions in jackrabbit-api, after all they
are still subject to change and it might well be that the interfaces will change before JCR
2.0 is final. Putting the extensions in jackrabbit-api implies that we are ready to offer
backwards compatibility to these new methods even if JCR 2.0 decides to drop them or implement
them in some other way. More on dev@ in a  moment...

> 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.


Mime
View raw message