[
https://issues.apache.org/jira/browse/OAK-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865442#comment-13865442
]
Thomas Mueller commented on OAK-327:
------------------------------------
With multi-valued properties, there is a difference between XPath "=" and "eq"
and so on. Here is a good explanation:
http://developer.marklogic.com/blog/comparison-operators-whats-the-difference
Basically, XPath "var = 5" means (for multi-valued properties) "is there any
value in var that is 5" where "var eq 5" means only matches for single-valued
properties (as far as I know).
As far as I know, this issue isn't currently a blocker, so unscheduling for
0.15.
> XPath 'eq' support and related
> -------------------------------
>
> Key: OAK-327
> URL: https://issues.apache.org/jira/browse/OAK-327
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: jcr
> Reporter: Alex Parvulescu
> Assignee: Thomas Mueller
> Fix For: 1.0
>
>
> Failing test SimpleQueryTest#testGeneralComparison.
> There is no support for 'eq' comparison in xpath currently: "@text eq 'foo'"
> fails to parse
> Jackrabbit 2.x actually supports more than just 'eq': it also supports not
> equal, and so on (see XPath specification).
> This is not required by the JCR 1.0 XPath spec, but we might still want to
> support it at some point for Jackrabbit 2.x compatibility. See also
> http://www.day.com/specs/jcr/1.0/6.6.4.11_Comparison_Operators.html
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
