[OAK-1739] Incorrect handling of multivalued comparisons in queries

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.0
• Component/s: core
• Assignee: Jukka Zitting
• Reporter: Jukka Zitting
• Created: 16/Apr/14 19:11
• Updated: 04/Jun/14 10:16
• Resolved: 16/Apr/14 19:32

Description

Section 6.7.14 of the JCR 2.0 spec says:

... operand1 may evaluate to an array of values (for example, the values of a multi-valued property), in which case the comparison is separately performed for each element of the array, and the Comparison constraint is satisfied as a whole if the comparison against any element of the array is satisfied.

This is currently not the case in Oak. Instead only the first value of the array is used in the comparison.

Issue Links

• is related to: OAK-1076 XPath failures for typed properties