[
https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932748#action_12932748
]
Doug Cutting commented on HADOOP-6685:
--------------------------------------
> I'm only adding ProtocolBuffers, which is a commonly used serialization
> format that many users including me find extremely useful.
Is there a strong reason to use ProtocolBuffers here rather than Avro, which is
already a dependency and provides similar functionality?
> The implementations are relatively small and are required for showing that
> the system actually works.
Then they could be included as tests. Also, if these uses are not the primary,
essential purpose of this functionality, perhaps patches for the issues that
are its primary use can be posted and they can be reviewed together.
> 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, 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.
