[
https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859550#action_12859550
]
Doug Cutting commented on HADOOP-6685:
--------------------------------------
Different serializations currently use common keys to share parts of their
configuration data. For example, many name a class that implements the
serialization. Several name a class that represents the instances. The code
that accesses these properties is shared, either through a common base class or
a utility class.
Binary blobs can also be considerably more fragile than a Map<String,String>.
If we wish the versions of clients and servers to be able to vary, then blobs
stored in configurations must be version-tolerant, i.e., written and read with
a fairly sophisticated serialization system.
> 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
>
> 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.
