[
https://issues.apache.org/jira/browse/HIVE-3972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572006#comment-13572006
]
Phabricator commented on HIVE-3972:
-----------------------------------
navis has commented on the revision "HIVE-3972 [jira] Support using multiple
reducer for fetching order by results".
INLINE COMMENTS
conf/hive-default.xml.template:1621 ok. It's harder than writing some codes.
ql/src/java/org/apache/hadoop/hive/ql/exec/RowFetcher.java:1 ah, ok.
ql/src/test/queries/clientpositive/orderby_query_bucketing.q:3 ok.
ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java:5604 It
will be calculated by input size, which might be 1 or not. Then it would be
safer assuming that it's not 1.
REVISION DETAIL
https://reviews.facebook.net/D8349
To: JIRA, navis
Cc: njain
> Support using multiple reducer for fetching order by results
> ------------------------------------------------------------
>
> Key: HIVE-3972
> URL: https://issues.apache.org/jira/browse/HIVE-3972
> Project: Hive
> Issue Type: Improvement
> Components: Query Processor
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-3972.D8349.1.patch, HIVE-3972.D8349.2.patch
>
>
> Queries for fetching results which have lastly "order by" clause make final
> MR run with single reducer, which can be too much. For example,
> {code}
> select value, sum(key) as sum from src group by value order by sum;
> {code}
> If number of reducer is reasonable, multiple result files could be merged
> into single sorted stream in the fetcher level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
