[ 
https://issues.apache.org/jira/browse/HADOOP-6438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790299#action_12790299
 ] 

Aaron Kimball commented on HADOOP-6438:
---------------------------------------

In MAPREDUCE-1126 you suggested that we add these methods directly to 
WritableSerialization and AvroSerialization. We could move them into the MR 
project proper, though I don't know that {{o.a.h.m.lib.input}} makes much sense 
as a destination -- these methods are configuring the intermediate data types, 
not the input types.

For future-proofing purposes: I anticipate that for MAPREDUCE-815, we'll also 
need to add related methods to set the serialization metadata maps for the 
final output key and value types. (a la {{JobConf.setOutputKeyClass()}}). It 
would be nice if the output type configuration and the intermediate type 
configuration remained "close together" (e.g., in the same package).

Should we add a new package that contains a configuration API around 
serializers? e.g.  {{o.a.h.m.lib.serialization}} or  {{o.a.h.m.lib.types}}

> Add configuration getters/setters to serialization classes
> ----------------------------------------------------------
>
>                 Key: HADOOP-6438
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6438
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>         Attachments: HADOOP-6438.patch
>
>
> Needed for MAPREDUCE-1126, getter and setter methods to inject specific 
> metadata into configurations to (de)serialize various data types.

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