hadoop-hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Thusoo (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HIVE-276) input3_limit.q fails under 0.17
Date Fri, 13 Feb 2009 00:50:59 GMT

    [ https://issues.apache.org/jira/browse/HIVE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673105#action_12673105
] 

Ashish Thusoo commented on HIVE-276:
------------------------------------

I think it is easier to just put a sort by in the final select.

SELECT * FROM T2 SORT BY T2.key, T2.value;


instead of

SELECT * FROM T2;



> input3_limit.q fails under 0.17
> -------------------------------
>
>                 Key: HIVE-276
>                 URL: https://issues.apache.org/jira/browse/HIVE-276
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Zheng Shao
>            Assignee: Zheng Shao
>         Attachments: HIVE-276.1.patch
>
>
> The plan ql/src/test/results/clientpositive/input3_limit.q.out shows that there are 2
map-reduce jobs:
> The first one is distributed and sorted as is specified by the query. The reducer side
has LIMIT 20.
> The second one (single reducer job imposed by LIMIT 20) does not have the same sort order,
so the final result is non-deterministic.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message