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 "David Gonzalez (JIRA)" <ji...@apache.org> on 2014/05/27 01:51:01 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=14009151#comment-14009151 ]
David Gonzalez commented on OAK-1752:
-------------------------------------
Also ran into this issue. Previously fast queries on JR2 are now slow.
Is there a stopgap recommendation on how to best approach this while the issues is triaged?
> 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
>
> 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)