[JCR-3498] OUTER JOIN behavior is improperly excluding some values

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: 2.6.1, 2.7.1
• Component/s: jackrabbit-core
• Assignee: Alex Deparvu
• Reporter: Randall Hauch
• Created: 23/Jan/13 18:11
• Updated: 13/May/13 09:44
• Resolved: 06/May/13 20:07

Description

Per JCR-3493, the OUTER JOIN behavior of Jackrabbit is improperly excluding nodes. For example, in a RIGHT OUTER JOIN, all the values on the right side of the join should be included, even if the right-hand-side's value in the join column is null. (In such cases, the results should always include the right-hand-side tuple and null values for the left hand side.) The same incorrect behavior is exhibited for LEFT OUTER JOINs.

JCR-3493 corrected the two test cases:

• org.apache.jackrabbit.test.api.query.qom.EquiJoinConditionTest#testRightOuterJoin1
• org.apache.jackrabbit.test.api.query.qom.EquiJoinConditionTest#testLeftOuterJoin2

add added these as known issues in the "jackrabbit-core/pom.xml" file; when this issue is corrected, those two known issues should be removed.

Issue Links

• depends upon: JCR-3493 OUTER JOIN tests expect incorrect results