hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nigel Daley (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 Thu, 25 Nov 2010 08:16:21 GMT

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

Nigel Daley commented on HADOOP-6685:
-------------------------------------

bq. Part of what has fueled the worst of this thread has been the complementary freezing of
the formats and serializations hosted in Hadoop

Hmm, reading thru this and related issue threads, I came to different conclusions on the fuel:
- historical bitterness
- lack of compromise on this patch
- thinly veiled attempts to snub others
- posting this patch on such a contentious issue so close to feature freeze of 0.22

bq. The existential question of the scope of Hadoop needs to be answered by the PMC, not navigated
by vetoes.

Nor, then, by unilateral reverting of patches like MAPREDUCE-1126 (the ultimate veto).  Maybe
it should have been reverted, but the way it was done still leaves me shaking my head.

> 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