[
https://issues.apache.org/jira/browse/MAPREDUCE-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1287:
-------------------------------------
Attachment: M1287-4.patch
I agree with Tom; this belongs in the framework if it's a legal optimization.
Should this be marked as an incompatible change, since the partitioner is
always called now? Clearly, any application that depends on the partitioner for
correctness can be rewritten, but is it worth calling out?
> HashPartitioner calls hashCode() when there is only 1 reducer
> -------------------------------------------------------------
>
> Key: MAPREDUCE-1287
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1287
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Affects Versions: 0.22.0
> Reporter: Ed Mazur
> Assignee: Ed Mazur
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: M1287-4.patch, MAPREDUCE-1287.2.patch,
> MAPREDUCE-1287.3.patch, MAPREDUCE-1287.patch
>
>
> HashPartitioner could be optimized to not call the key's hashCode() if there
> is only 1 reducer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
