[OAK-6776] Correctly use IndexPlan.supportsPathRestrictions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.12, 1.8.0
• Component/s: query
• Epic Link: indexer resilience
• Sprint: L15
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 03/Oct/17 07:27
• Updated: 08/Oct/19 15:21
• Resolved: 15/Nov/17 11:05

Description

Right now, IndexPlan.supportsPathRestrictions (introduced in OAK-6734) is used in the query engine for some kind of mixed "rule based" and "cost based" query optimization.

I think the current implementation isn't correct, as (for example) a query with multiple indexes will now use the wrong index in some cases (for example property index, even if the cost of the Lucene index is lower).

Also, if there is a Lucene index with supportsPathRestrictions, and one without, right now always the one with supportsPathRestrictions is used. This is probably better right now, but once OAK-6735 is resolved, this should be fixed as well.

Issue Links

• relates to: OAK-6734 IndexPlan: add supportsPathRestrictions