You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Thomas Mueller (JIRA)" <ji...@apache.org> on 2014/04/29 15:11:15 UTC
[jira] [Resolved] (OAK-1776) Ordered index returns the wrong nodes
when ordering by relative properties
[ https://issues.apache.org/jira/browse/OAK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Mueller resolved OAK-1776.
---------------------------------
Resolution: Fixed
> Ordered index returns the wrong nodes when ordering by relative properties
> --------------------------------------------------------------------------
>
> Key: OAK-1776
> URL: https://issues.apache.org/jira/browse/OAK-1776
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: query
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Fix For: 1.0, 1.1
>
> Attachments: OAK-1776.patch
>
>
> The ordered index returns the wrong nodes (the child nodes) when the "order by" uses a relative path for the property name. Example:
> {noformat}
> select * from [nt:file] order by [jcr:content/jcr:lastModified]
> {noformat}
> This query returns the nodes at level "jcr:content" (the child nodes) instead of the nodes at level "nt:file".
--
This message was sent by Atlassian JIRA
(v6.2#6252)