[
https://issues.apache.org/jira/browse/JCR-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615025#comment-13615025
]
Ati Rosselet commented on JCR-3498:
-----------------------------------
I also seem to have run into this issue - I spend almost 2 days banging my head
against a wall until I found this JIRA entry. This seems like a pretty major
issue - any word on possible resolution?
> OUTER JOIN behavior is improperly excluding some values
> -------------------------------------------------------
>
> Key: JCR-3498
> URL: https://issues.apache.org/jira/browse/JCR-3498
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.5.2
> Reporter: Randall Hauch
> Fix For: 2.7
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
