[jira] [Commented] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

["Sudheesh Katkam (JIRA)" <ji...@apache.org>]

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

Sudheesh Katkam commented on DRILL-2167:
----------------------------------------

After DRILL-2083 was fixed, the queries mentioned produce correct number of records. But the results of the first mentioned query are not ordered. Fix to DRILL-2838 will most likely fix this issue (s.rms is null).

> Order by on a repeated index from the output of a flatten on large no of records results in incorrect results
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-2167
>                 URL: https://issues.apache.org/jira/browse/DRILL-2167
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Relational Operators
>            Reporter: Rahul Challapalli
>            Assignee: Sudheesh Katkam
>            Priority: Critical
>             Fix For: 1.0.0
>
>         Attachments: data.json
>
>
> git.commit.id.abbrev=3e33880
> The below query results in 200006 records. Based on the data set we should only receive 200000 records. 
> {code}
> select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s order by s.rms.rptd[1].d;
> {code}
> When I removed the order by part, drill correctly reported 200000 records.
> {code}
> select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
> {code}
> I attached the data set with 2 records. I copied over the data set 50000 times and ran the queries on top of it. Let me know if you have any other questions



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