[
https://issues.apache.org/jira/browse/MAPREDUCE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805166#action_12805166
]
Owen O'Malley commented on MAPREDUCE-1126:
------------------------------------------
{quote}
Well, ok, guess I'm in the minority on that instinct
{quote}
No, that is pretty constant from the users. :)
My assertion is that leaving the type as the primary instrument of the user in
defining the job is correct. I haven't talked to *any* users that care about
using a non-default serializer for a given type.
I certainly do want Avro to go through the MapReduce pipeline. I guess I'll
need to implement a prototype to make it clear how Avro-based MapReduce could
work without a massively incompatible user-facing change.
> 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.
