You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/08/27 11:40:57 UTC

[jira] [Commented] (OAK-1752) Node name queries should use an index

    [ https://issues.apache.org/jira/browse/OAK-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14112091#comment-14112091 ] 

Thomas Mueller commented on OAK-1752:
-------------------------------------

> Is there a stopgap recommendation

I suggest to use a property (for example called "nodeName") and index it. The advantage over a full node name index (that indexes every node in the repository) is that you only index those nodes that you are interested in. This makes the index much more efficient (both to update and to query).

> Node name queries should use an index
> -------------------------------------
>
>                 Key: OAK-1752
>                 URL: https://issues.apache.org/jira/browse/OAK-1752
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: query
>            Reporter: Alex Parvulescu
>             Fix For: 1.1, 1.0.6
>
>
> The node name queries don't use any index currently, making them really slow and triggering a lot of traversal warnings.
> Simply adding node names to a property index would be too much content indexed, but as Lucene already indexes the node names, using this index would be one viable option.
> {code}
> /jcr:root//*[fn:name() = 'jcr:content']
> /jcr:root//*[jcr:like(fn:name(), 'jcr:con%')] 
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)