[ 
https://issues.apache.org/jira/browse/MAPREDUCE-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829266#action_12829266
 ] 

Jay Booth commented on MAPREDUCE-1126:
--------------------------------------

Yeah, I'm definitely not a stakeholder in this issue or in low-level mapreduce 
in general, but was just saying if we're throwing around the idea of an 
entirely new underlying API anyways, maybe now would be the time to consider 
that -- it'd be pretty simple to wrap the existing API around the concept if it 
were baked into the lower-level API, but it'd be harder to add the concept to 
the lower-level API once it's already solidified.

Either way, I don't have the mojo to make a big push for it, was just throwing 
the idea out there if it's decided to go forward with a different underlying 
API.

> 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, 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.

Reply via email to