[OAK-1171] Query fails unexpectedly when property conversion is not possible

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.11
• Component/s: jcr, query
• Assignee: Alex Deparvu
• Reporter: Alexander Klimetschek
• Created: 13/Nov/13 03:44
• Updated: 21/Nov/13 10:30
• Resolved: 13/Nov/13 15:35

Description

A simple xpath query for a string property doesn't work when there is a long (or other inconvertible) property under the same name anywhere in the repository.

To reproduce:

• Create a LONG property: /test/@property = 1
• Run this query: //*[property = "foo"]

This will throw a NumberFormatException at o.a.j.o.plugins.value.Conversions$Converter.toLong(Conversions.java:80) and fail the query.

Jackrabbit 2 works well here and simply does not include a match for that node in the result. While I can see that Oak seems to implement the JCR 2.0 spec here:

If operand1 and operand2 evaluate to values of different property types, the value of operand2 is converted to the property type of the value of operand1 as described in §3.6.4 Property Type Conversion. If the type conversion fails, the query is invalid.

... I don't think this makes any sense. If conversion does not work, this is simply not a match, but it must not break the query.

Issue Links

• relates to: OAK-1076 XPath failures for typed properties