[JCR-2852] Support multi-selector OR constraints in join queries

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.2.7
• Component/s: jackrabbit-core, query
• Assignee: Alex Deparvu
• Reporter: Jukka Zitting
• Created: 22/Dec/10 09:20
• Updated: 08/Nov/11 15:47
• Resolved: 23/May/11 15:08

Description

Our current join implementation doesn't support OR constraints that refer to more than one selector. For example the following query is not possible:

SELECT a.* FROM [my:type] AS a INNER JOIN [my:type] as b ON a.foo = b.bar WHERE a.baz = 'x' OR b.baz = 'y'

This limitation is a result of the way the join execution splits the query into per-selector components and merges the result based on the given join condition.

A simple but often inefficient solution would be to process such OR constraints as post-processing filters like we already do for some other more complex constraint types.

Issue Links

• is part of: JCR-2933 SQL2 Left Outer Join
• is superceded by: JCR-3000 SQL2 Join with OR clause still has some issues