[jira] [Commented] (ASTERIXDB-1531) Order by bug for composite order keys and nested fields

["Yingyi Bu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378676#comment-15378676 ] 

Yingyi Bu commented on ASTERIXDB-1531:
--------------------------------------

After looking at the data, I realized that you have to change "screen-name" to "screenName":

from $cm in dataset ChirpMessages
order by $cm.user.screenName, $cm.chirpid
select $cm;

Otherwise, the data is ordered by MISSING first (as $cm.user.screen-name evaluates to MISSING in the data) and then $cm.chirpid :-)

> Order by bug for composite order keys and nested fields
> -------------------------------------------------------
>
>                 Key: ASTERIXDB-1531
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1531
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Translator - AQL
>         Environment: 101-like demo (modified TinySocial) on current/latest binary bits for Mac
>            Reporter: Michael J. Carey
>            Assignee: Yingyi Bu
>         Attachments: tinysocialnew.zip
>
>
> use dataverse TinySocial;  // okay, a name-modified version thereof
> from $cm in dataset ChirpMessages
> order by $cm.user.screen-name, $cm.chirpid
> select $cm;
> ---> This just orders by chirpid.  (You can repro by doing the same thing with the current TinySocial data using the non-renamed stuff - so I won't attach all the repro stuff here unless you want me too, in which case I can.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)