hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (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 Wed, 01 Dec 2010 19:18:20 GMT

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

Sanjay Radia commented on HADOOP-6685:
--------------------------------------

@Doug> Progress stopped on HADOOP-6659 when Eric vetoed my incremental approach
Doug, at least a couple of folks asked for a design doc and fuller plan; you did not provide
it.

Doug you added a dependency on Avro in RPC without providing a plan on how all the pieces
are put together. Indeed it is more than just a library dependency - there are avro related
annotations. While I am a fan of Avro (being part of the team that created it at Yahoo), I
see no problems in adding first class support for PB since it is a robust serialization framework.

When I let the Avro dependency creep into Hadoop I did not think that Doug would be opposed
to adding support for PB in the future. Both need to be supported in 
a first class way. My feeling is that Avro will prevail in the long term but right now PB
addresses the needs of many users.



> 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