[
https://issues.apache.org/jira/browse/OAK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated OAK-1076:
-------------------------------
Attachment: 0001-OAK-1076-XPath-failures-for-typed-properties.patch
The attached patch fixes the evaluation of this and other multivalued
comparisons.
I'm not sure which one is the better approach here:
* Apply the patch now for 1.0, even though it (correctly, I'd argue) changes
how some query constraints are evaluated and thus could have impact on existing
clients.
* File a new issue for this and mark it as a known issue for 1.0. Just disable
the troublesome test case in 1.0 to allow the build to pass on Java 8.
WDYT?
> XPath failures for typed properties
> -----------------------------------
>
> Key: OAK-1076
> URL: https://issues.apache.org/jira/browse/OAK-1076
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, query
> Reporter: Alex Parvulescu
> Assignee: Thomas Mueller
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 0001-OAK-1076-XPath-failures-for-typed-properties.patch,
> OAK-1076-b.patch, OAK-1076.patch
>
>
> It looks like there are some failures in xpath queries that expect a match
> only on properties of a certain type (which is to be inferred from the query)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
