[
https://issues.apache.org/jira/browse/HIVE-2495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13150604#comment-13150604
]
iryoung jeong commented on HIVE-2495:
-------------------------------------
I think, you mentioned about "mapred.reduce.tasks.force" means there're some
situations when "mapred.reduce.tasks" is not working.
For example, ORDER BY col1 SQL statement should run on only 1 reducer because
it requires global sorting.
So I wonder if "mapred.reduce.tasks.force" is set, should reducers numbers
always apply for every case even though result can be incorrect?
anyway, more detailed scenario will be helpful.
> set mapred.reduce.tasks does not work
> -------------------------------------
>
> Key: HIVE-2495
> URL: https://issues.apache.org/jira/browse/HIVE-2495
> Project: Hive
> Issue Type: Bug
> Reporter: Jander G
>
> Setting mapred.reduce.tasks does not work. In my opinion, we should provider
> a property (eg. mapred.reduce.tasks.force) to make "mapred.reduce.tasks"
> working. Thus there is a way to set a constant reduce for experienced people.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
