Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
Reviewed
Description
Currently the key comparator is defined as a Java class. Instead we should use the Serialization API to create key comparators. This would permit, e.g., Avro-based comparators to be used, permitting efficient sorting of complex data types without having to write a RawComparator in Java.
Attachments
Attachments
Issue Links
- blocks
-
MAPREDUCE-815 Add AvroInputFormat and AvroOutputFormat so that hadoop can use Avro Serialization
- Resolved
- depends upon
-
HADOOP-6438 Add configuration getters/setters to serialization classes
- Resolved
-
HADOOP-6420 String-to-String Maps should be embeddable in Configuration
- Closed
-
HADOOP-6443 Serialization classes accept invalid metadata
- Closed
- is blocked by
-
HADOOP-6323 Serialization should provide comparators
- Closed
- is related to
-
MAPREDUCE-1183 Serializable job components: Mapper, Reducer, InputFormat, OutputFormat et al
- Open
-
MAPREDUCE-1360 Record skipping should work with more serializations
- Open
- relates to
-
MAPREDUCE-1462 Enable context-specific and stateful serializers in MapReduce
- Open
-
MAPREDUCE-1452 Add a low-level MapReduce API
- Resolved