[
https://issues.apache.org/jira/browse/HADOOP-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964962#action_12964962
]
Chris Douglas commented on HADOOP-6685:
---------------------------------------
Doug> I'll try to be clearer. As I understand the veto, you and Tom object to
three points:
# Format of the serialized metadata, specifically you both prefer
JSON/stringly-typed data to protocol buffers
# Packaging, in particular adding protocol buffers and thrift
# Changing SequenceFile, an experimental format packaged with Hadoop
I'm suggesting that this issue focus on (1) exclusively. If we reach consensus
on this point, then we can commit a patch and address (2) and (3) elsewhere.
There is agreement on the domain of (1), so a technical debate may follow. In
contrast, (2) and (3) can be deferred, as (2) is part of a larger failing and
(3) can be addressed after the patch is committed. While (1) admits coherent
arguments, (2-3) have been fought by indignation. As a tactic for consensus, it
seems reasonable to stop arguing project policy proxied through this patch and
focus on the item admitting technical, falsifiable claims.
> 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.
