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

Doug Cutting commented on MAPREDUCE-1126:
-----------------------------------------

> Doug, neither this or my previous patch use any deprecated APIs.

They use a method (SerializationBase.getMetadataFromClass) that's not intended 
as a primary, serialization-independent means for the framework to create a 
serialization.  That's a utility intended to be shared by serialization systems 
that use a class to create their metadata.  The only other calls to it are from 
deprecated, back-compatibility methods and contexts where serialization is 
class-based.  It *should* have been deprecated.  New framework code should not 
use this method as a primary means to create a serialization, as it does not 
support all serializations.


> 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: m-1126-2.patch, m-1126-3.patch, 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