[
https://issues.apache.org/jira/browse/HADOOP-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13038714#comment-13038714
]
Todd Lipcon commented on HADOOP-7328:
-------------------------------------
I don't think it's an incompatible change to replace what's currently a
NullPointerException with something more descriptive. If the method signature
can't throw an IOException, at least a RuntimeException with a nice error
message would be an improvement. (To be clear, I'm not talking about changing
the serialization factory, but rather the point in MR where the NPE gets thrown
because of the null serializer)
> Give more information about a missing Serializer class
> ------------------------------------------------------
>
> Key: HADOOP-7328
> URL: https://issues.apache.org/jira/browse/HADOOP-7328
> Project: Hadoop Common
> Issue Type: Improvement
> Components: io
> Affects Versions: 0.20.2
> Reporter: Harsh J Chouraria
> Assignee: Harsh J Chouraria
> Labels: io, serialization
> Fix For: 0.23.0
>
> Attachments: HADOOP-7328.r1.diff
>
>
> When you have a key/value class that's non Writable and you forget to attach
> io.serializers for the same, an NPE is thrown by the tasks with no
> information on why or what's missing and what led to it. I think a better
> exception can be thrown by SerializationFactory instead of an NPE when a
> class is not found accepted by any of the loaded ones.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
