You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2009/03/27 13:46:50 UTC
[jira] Created: (JCR-2044) Pass result resultFetchSize/limit hint
to SortedLuceneQueryHits
Pass result resultFetchSize/limit hint to SortedLuceneQueryHits
---------------------------------------------------------------
Key: JCR-2044
URL: https://issues.apache.org/jira/browse/JCR-2044
Project: Jackrabbit Content Repository
Issue Type: Improvement
Reporter: Marcel Reutegger
Priority: Minor
The SortedLuceneQueryHits currently uses a default value of 100 (taken from lucene) for initially retrieved and sorted results. For larger result sets this is not optimal because it will cause re-execution of the underlying query with values 200, 400, 800, 1600, 3200, 6400, etc. Instead the query hits should get the limit that is set on the query or the resultFetchSize configured for the SearchIndex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2044) Pass resultFetchSize/limit hint to
SortedLuceneQueryHits
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-2044:
----------------------------------
Summary: Pass resultFetchSize/limit hint to SortedLuceneQueryHits (was: Pass result resultFetchSize/limit hint to SortedLuceneQueryHits)
> Pass resultFetchSize/limit hint to SortedLuceneQueryHits
> --------------------------------------------------------
>
> Key: JCR-2044
> URL: https://issues.apache.org/jira/browse/JCR-2044
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Marcel Reutegger
> Priority: Minor
>
> The SortedLuceneQueryHits currently uses a default value of 100 (taken from lucene) for initially retrieved and sorted results. For larger result sets this is not optimal because it will cause re-execution of the underlying query with values 200, 400, 800, 1600, 3200, 6400, etc. Instead the query hits should get the limit that is set on the query or the resultFetchSize configured for the SearchIndex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-2044) Pass resultFetchSize/limit hint to
SortedLuceneQueryHits
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-2044.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Applied patch in revision: 759889
> Pass resultFetchSize/limit hint to SortedLuceneQueryHits
> --------------------------------------------------------
>
> Key: JCR-2044
> URL: https://issues.apache.org/jira/browse/JCR-2044
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: JCR-2044.patch
>
>
> The SortedLuceneQueryHits currently uses a default value of 100 (taken from lucene) for initially retrieved and sorted results. For larger result sets this is not optimal because it will cause re-execution of the underlying query with values 200, 400, 800, 1600, 3200, 6400, etc. Instead the query hits should get the limit that is set on the query or the resultFetchSize configured for the SearchIndex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-2044) Pass resultFetchSize/limit hint to
SortedLuceneQueryHits
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger updated JCR-2044:
----------------------------------
Attachment: JCR-2044.patch
Proposed patch.
> Pass resultFetchSize/limit hint to SortedLuceneQueryHits
> --------------------------------------------------------
>
> Key: JCR-2044
> URL: https://issues.apache.org/jira/browse/JCR-2044
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Reporter: Marcel Reutegger
> Priority: Minor
> Attachments: JCR-2044.patch
>
>
> The SortedLuceneQueryHits currently uses a default value of 100 (taken from lucene) for initially retrieved and sorted results. For larger result sets this is not optimal because it will cause re-execution of the underlying query with values 200, 400, 800, 1600, 3200, 6400, etc. Instead the query hits should get the limit that is set on the query or the resultFetchSize configured for the SearchIndex.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.