You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Paco Avila (JIRA)" <ji...@apache.org> on 2007/06/11 11:26:26 UTC
[jira] Commented: (JCR-967) Only search the index for the
"jcr:system" tree if needed
[ https://issues.apache.org/jira/browse/JCR-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503349 ]
Paco Avila commented on JCR-967:
--------------------------------
But you can exclude jcr:system from the search query, isn't it? In my application my queries start from my "root node" not from the repository root.
> Only search the index for the "jcr:system" tree if needed
> ---------------------------------------------------------
>
> Key: JCR-967
> URL: https://issues.apache.org/jira/browse/JCR-967
> Project: Jackrabbit
> Issue Type: Improvement
> Components: query
> Affects Versions: 1.3
> Reporter: Christoph Kiehl
>
> Right now every time a query is executed the index of the current workspace as well as the index of the "jcr:system" tree is searched. A lot of queries are not searching in the "jcr:system" tree at all therefore it should be checked if the query contains paths that include "jcr:system". There are two relevant nodes in the query tree to find that out:
> - what's the first location step and does it include the jcr:system tree? I think that's an easy one.
> - does the query contain a jcr:deref node? If there is an intermediate result of a query may dereference into the jcr:system tree.
> This should notably speed up query execution if you are working extensively with versioning.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.