[OAK-1965] Support for constraints like: foo = 'X' OR bar = 'Y'

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Component/s: core, query
• Assignee: Jukka Zitting
• Reporter: Jukka Zitting
• Created: 11/Jul/14 04:52
• Updated: 25/Feb/16 10:55
• Resolved: 17/Jul/14 14:21

Description

Consider the following query statement:

SELECT * FROM [nt:base] WHERE [foo] = 'X OR [bar] = 'Y'

Such a query could be fairly efficiently executed against a property index that indexes the values of both "foo" and "bar" properties. However, the query engine doesn't pass such OR constraints down to the index implementations, so we currently can't leverage such an index for this query.

Issue Links

• is related to: OAK-1617 Automatically convert "or" queries to "union" for SQL-2