You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/30 19:30:40 UTC

[jira] [Resolved] (HADOOP-6685) Change the generic serialization framework API to use serialization-specific bytes instead of Map for configuration

     [ https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HADOOP-6685.
--------------------------------------

    Resolution: Won't Fix

Closing this as Won't Fix since consensus will clearly never be reached.

(JIRA needs a 'Hung Jury' resolution option!)

> Change the generic serialization framework API to use serialization-specific bytes instead of Map<String,String> for configuration
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6685
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6685
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>         Attachments: SerializationAtSummit.pdf, serial.patch, serial4.patch, serial6.patch, serial7.patch, serial9.patch
>
>
> Currently, the generic serialization framework uses Map<String,String> for the serialization specific configuration. Since this data is really internal to the specific serialization, I think we should change it to be an opaque binary blob. This will simplify the interface for defining specific serializations for different contexts (MAPREDUCE-1462). It will also move us toward having serialized objects for Mappers, Reducers, etc (MAPREDUCE-1183).



--
This message was sent by Atlassian JIRA
(v6.2#6252)