[HADOOP-6685] Change the generic serialization framework API to use serialization-specific bytes instead of Map<String,String> for configuration

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Hadoop Flags: Incompatible change
• Assignee: Owen O'Malley
• Reporter: Owen O'Malley
• Created: 06/Apr/10 17:24
• Updated: 30/Jul/14 17:29
• Resolved: 30/Jul/14 17:29

Description

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).

Issue Links

• blocks: HADOOP-6684 Create a wrapper for TFile that handles generic serialization
• blocks: MAPREDUCE-1462 Enable context-specific and stateful serializers in MapReduce
• incorporates: HADOOP-10860 Add serialization for Protocol Buffers
• incorporates: MAPREDUCE-376 Add serialization for Thrift
• is blocked by: HADOOP-6698 Revert the io.serialization package to 0.20.2's api
• is related to: THRIFT-363 Maven Deploy