hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-6685) Change the generic serialization framework API to use serialization-specific bytes instead of Map<String,String> for configuration
Date Fri, 19 Nov 2010 05:32:19 GMT

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

Arun C Murthy commented on HADOOP-6685:
---------------------------------------

{quote}
For those of us not as familiar with the relevant code, could someone summarize how changing
this particular interface from Map<String,String> to byte[] significantly simplifies
the implementation of MAPREDUCE-1462 and MAPREDUCE-1183? This isn't readily apparent from
reading this jira or MAPREDUCE-1126, which seems largely orthogonal. 
{quote}

This discussion is about interface design, especially on an interface which has significant
impact on MR user-facing APIs, not necessarily about easing implementation of MAPREDUCE-1183
or MAPREDUCE-1126.

MAPREDUCE-1126 should have been orthogonal, but it made significant changes to Map-Reduce
APIs which led to this debate. 

I understand it's hard to cold-start on MAPREDUCE-1126, maybe you can start with: http://s.apache.org/MR1126.
Hopefully that provides some context.

> 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
>             Fix For: 0.22.0
>
>         Attachments: libthrift.jar, serial.patch, serial4.patch, serial6.patch, serial7.patch,
SerializationAtSummit.pdf
>
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message