[
https://issues.apache.org/jira/browse/MAPREDUCE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802571#action_12802571
]
Doug Cutting commented on MAPREDUCE-1126:
-----------------------------------------
Would this change be more palatable if we used a shorter term than "JobData",
instead just calling it "Data"? Combined with changing the setters to accept a
JobContext directly, this would look like:
{code}
- job.setMapOutputKeyClass(LongWritable.class);
- job.setMapOutputValueClass(BytesWritable.class);
+ WritableData.setMapOutputKeyClass(job, LongWritable.class);
+ WritableData.setMapOutputValueClass(job, BytesWritable.class);
{code}
Is that better?
> shuffle should use serialization to get comparator
> --------------------------------------------------
>
> Key: MAPREDUCE-1126
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1126
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: task
> Reporter: Doug Cutting
> Assignee: Aaron Kimball
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1126.2.patch, MAPREDUCE-1126.3.patch,
> MAPREDUCE-1126.4.patch, MAPREDUCE-1126.5.patch, MAPREDUCE-1126.6.patch,
> MAPREDUCE-1126.patch
>
>
> Currently the key comparator is defined as a Java class. Instead we should
> use the Serialization API to create key comparators. This would permit,
> e.g., Avro-based comparators to be used, permitting efficient sorting of
> complex data types without having to write a RawComparator in Java.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
