[
https://issues.apache.org/jira/browse/HIVE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732735#action_12732735
]
Namit Jain commented on HIVE-647:
---------------------------------
order by should use only 1 reducer - if you see otherwise, can you update the
jira
sort behavior is as expected - you are not guaranteed that the first query
returns sorted results, it just happens to be sorted, probably the first
reducer had more than 50 records which were returned.
if order by does work, you can close this jira.
> SORT BY with GROUP ignored without LIMIT
> ----------------------------------------
>
> Key: HIVE-647
> URL: https://issues.apache.org/jira/browse/HIVE-647
> Project: Hadoop Hive
> Issue Type: Bug
> Components: Query Processor
> Reporter: Bill Graham
>
> For queries with GROUP BY and SORT BY, the sort is not handled properly when
> a LIMIT is not supplied. If I run the following two queries, the first
> returns properly sorted results. The second does not.
> SELECT user, SUM(numRequests) AS num FROM MyTable GROUP BY user SORT BY num
> DESC LIMIT 50;
> SELECT user, SUM(numRequests) AS num FROM MyTable GROUP BY user SORT BY num
> DESC;
> Explain is different for the two queries as well. The first uses 3 M/R jobs
> and the second only uses 2, which might be part of the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.