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 2008/02/19 16:52:43 UTC
[jira] Created: (JCR-1397) Allow query results with unknown size
Allow query results with unknown size
-------------------------------------
Key: JCR-1397
URL: https://issues.apache.org/jira/browse/JCR-1397
Project: Jackrabbit
Issue Type: Improvement
Components: jackrabbit-core
Reporter: Marcel Reutegger
Priority: Minor
To further optimize certain queries the query implementation should be changed to allow for unknown result sizes. Currently there is only one query ( //* ) where the query result returns an unknown size and a special query result implementation is returned. At the same time, this should be fixed that only one implementation is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1397) Allow query results with unknown size
Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1397.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5
QueryHits is now an interface and there are two implementations: LuceneQueryHits and NodeTraversingQueryHits.
Implemented in revision: 629145
> Allow query results with unknown size
> -------------------------------------
>
> Key: JCR-1397
> URL: https://issues.apache.org/jira/browse/JCR-1397
> Project: Jackrabbit
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Marcel Reutegger
> Priority: Minor
> Fix For: 1.5
>
>
> To further optimize certain queries the query implementation should be changed to allow for unknown result sizes. Currently there is only one query ( //* ) where the query result returns an unknown size and a special query result implementation is returned. At the same time, this should be fixed that only one implementation is used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.