[OAK-1894] PropertyIndex only considers the cost of a single indexed property

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.2, 1.1.0
• Component/s: query
• Assignee: Thomas Mueller
• Reporter: Justin Edelson
• Created: 16/Jun/14 14:53
• Updated: 08/Oct/19 15:21
• Resolved: 23/Jun/14 11:17

Description

The existing PropertyIndex loops through the PropertyRestriction objects in the Filter and essentially only calculates the cost of the first indexed property. This isn't actually the first property in the query and Filter.propertyRestrictions is a HashMap.

More confusingly, the plan for a query with multiple indexed properties outputs all indexed properties, even though only the first one is used.

For queries with multiple indexed properties, the cheapest property index should be used in all three relevant places: when calculating the cost, when executing the query, and when producing the plan.

Issue Links

• relates to: OAK-1908 Improved query plan for PropertyIndex and OrderedIndex