Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
0.20.2
-
None
-
serializers
Description
As discussed on HADOOP-7328, MapReduce can handle serializers in a much better way in case of bad configuration, improper imports (Some odd Text class instead of the Writable Text set as key), etc..
This issue covers the MapReduce parts of the improvements (made to IFile, MapOutputBuffer, etc. and possible early-check of serializer availability pre-submit) that provide more information than just an NPE as is the current case.
Attachments
Attachments
Issue Links
- depends upon
-
HADOOP-7328 When a serializer class is missing, return null, not throw an NPE.
- Resolved
- is duplicated by
-
MAPREDUCE-5728 Check NPE for serializer/deserializer in MapTask
- Patch Available
- is related to
-
HADOOP-8531 SequenceFile Writer can throw out a better error if a serializer or deserializer isn't available
- Closed