[OAK-1752] Node name queries should use an index

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.21, 1.2.6, 1.3.6, 1.4
• Component/s: query
• Labels: performance
• Epic Link: Query performance improvements
• Assignee: Chetan Mehrotra
• Reporter: Alex Deparvu
• Created: 22/Apr/14 09:15
• Updated: 08/Oct/19 15:21
• Resolved: 03/Sep/15 11:09

Description

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.

/jcr:root//*[fn:name() = 'jcr:content']
/jcr:root//*[jcr:like(fn:name(), 'jcr:con%')] 

Issue Links

• is related to: OAK-4814 Add orderby support for nodename index

Sub-Tasks

• QueryEngine should expose name query as property restriction: Closed