[OAK-1776] Ordered index returns the wrong nodes when ordering by relative properties

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0
• Component/s: query
• Assignee: Thomas Mueller
• Reporter: Thomas Mueller
• Created: 29/Apr/14 08:49
• Updated: 04/Jun/14 10:16
• Resolved: 29/Apr/14 13:10

Description

The ordered index returns the wrong nodes (the child nodes) when the "order by" uses a relative path for the property name. Example:

select * from [nt:file] order by [jcr:content/jcr:lastModified]

This query returns the nodes at level "jcr:content" (the child nodes) instead of the nodes at level "nt:file".