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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/09/03 13:38:46 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=14728890#comment-14728890 ] 

Chetan Mehrotra commented on OAK-1752:
--------------------------------------

Updated docs. Refer to http://jackrabbit.apache.org/oak/docs/query/lucene.html#index-node-name for usage details

> 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
>            Assignee: Chetan Mehrotra
>              Labels: performance
>             Fix For: 1.0.20, 1.3.6, 1.2.5
>
>         Attachments: OAK-1752.patch
>
>
> 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.3.4#6332)