[
https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932392#action_12932392
]
Luke Lu commented on HADOOP-6685:
---------------------------------
THRIFT-363 addresses the thrift maven deploy, even though it's not completely
resolved. We should help resolving it, as they're voting for the 0.6.0 release.
Checking in an external dependency should be the last resort as any projects
(hdfs, mapreduce etc. along with their contrib srcs) that depend on
hadoop-common artifacts will have to be modified manually to include the jar in
the source trees. libthrift.jar needs a version string (e.g.
libthrift-0.5.0.jar) as well, if we decide to check it in.
> 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.
