[OAK-4904] For unique indexes avoid consulting indexes other than property index

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.5.12, 1.6.0
• Component/s: query
• Labels: performance
• Assignee: Thomas Mueller
• Reporter: Chetan Mehrotra
• Created: 07/Oct/16 09:49
• Updated: 13/Sep/21 09:48
• Resolved: 07/Oct/16 12:35

Description

Currently for queries involving unique index like

SELECT * FROM [nt:base] WHERE [jcr:uuid] = $id

QueryEngine would start consulting all types of index in order of minimum cost. Where minimum cost are

• PropertyIndex - 2.0
• LucenePropertyIndex - 2.1

For such queries in case of match property index returns a cost of (base) 2 + (count) 1 = 3 due to which QE has to consult Lucene index also. Given such queries a very frequent it would be better to avoid consulting Lucene index as that adds unnecessary overhead

Issue Links

• is related to: OAK-4081 Faster cost calculation for property indexes and traversal
• relates to: OAK-4412 Lucene hybrid index