[
https://issues.apache.org/jira/browse/OAK-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-1752:
---------------------------------
Attachment: OAK-1752.patch
[patch|^OAK-1752.patch] for the same. It depends upon the patch in OAK-2634.
* Node names would be index against a Lucene field named {{:nodeName}}
* Supports equals and like queries
* To enable this support one need to set {{indexNodeName}} to true in the
indexRule for that nodeType
Later we can look into possibility of using custom tokenizer to index the node
name differently. For e.g. for nt:file we can configure a camelCase tokenizer
to extract multiple fields. This would avoid using expensive like query to
lookup file by partial names
[~alexparvulescu] [~tmueller] Can you have a look and provide feedback
> 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
> Fix For: 1.2
>
> 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)
