[OAK-7850] Indexes that don't support facets being queried should not participate in execution plan

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.10.0, 1.9.11, 1.8.10, 1.6.16
• Component/s: lucene
• Assignee: Vikas Saurabh
• Reporter: Vikas Saurabh
• Created: 18/Oct/18 11:54
• Updated: 22/Oct/19 13:59
• Resolved: 04/Nov/18 12:46

Description

Currently we can have a case where a query with facets can be answered by an index which can resolve all the constraints but don't have facets configured. At times this index might even win the cost war even if there could be an alternative index which might report to be more expensive but can answer the facets.

While it's not a good practice to have competing indexes, but index selection could have been smarter anyway.

Issue Links

• is depended upon by: OAK-7608 Throw exception if all properties name are given wrong for faceting
• is related to: OAK-8711 Queries with facets should not use traversal