[OAK-2263] Avoid unnecessary reads on index lookup

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Component/s: core
• Assignee: Marcel Reutegger
• Reporter: Marcel Reutegger
• Created: 11/Nov/14 13:00
• Updated: 01/Mar/16 13:53
• Resolved: 16/Mar/15 08:04

Description

The PropertyIndex looks up the matching index definitions multiple times. This means each time all definitions are read to find out which one matches the given property restriction. AFAICS this happens at least six times. The first two times when the cost is calculated: 1) check if the property is indexed and 2) calculate the cost. The next four times when the query is executed: 3) check if the property is indexed, 4) calculate the cost, 5) check if the property is indexed, 6) lookup index to create cursor for query.

Issue Links

• duplicates: OAK-1273 Reduce overhead when handling many parallel property indices
• relates to: OAK-2679 Query engine: faster cost calculation