[OAK-7254] Indexes with excludedPaths, or includedPaths should not be picked for queries without path

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.16.0
• Component/s: lucene, query
• Labels: indexingPatch mohit
• Epic Link: indexer resilience
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 08/Feb/18 13:20
• Updated: 25/Dec/22 01:58
• Resolved: 10/Jul/19 13:21

Description

Queries that don't have a clear path restriction should not use indexes that have excludedPaths or includedPaths set, except in some exceptional cases (to be defined).

For example, if a query doesn't have a path restriction, say:

/jcr:root//element(*, nt:base)[@status='RUNNING']

Then an index that has excludedPaths set (for example to /etc) shouldn't be used, at least not if a different index is available. Currently it is used currently, actually in favor of another index, if the property "status" is commonly used in /etc. Because of that, the index that doesn't have excludedPath has a higher cost (as it indexes the property "status" in /etc, and so has more entries for "status", than the index that doesn't index /etc).

The same for includedPaths, in case queryPaths isn't set to the same value(s).

Issue Links

• links to: GitHub Pull Request #132