[
https://issues.apache.org/jira/browse/HADOOP-7328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated HADOOP-7328:
----------------------------
Attachment: 0.22-HADOOP-7328.r7.diff
0.23-HADOOP-7328.r7.diff
HADOOP-7328.r7.diff
Patches with Todd's comments fixed. Patches for 0.22, 0.23, Trunk.
Please review and let me know if further additions are required!
Will also be updating the dependent JIRA patches for trunk, meanwhile, for this
new behavior.
> When a serializer class is missing, return null, not throw an NPE.
> ------------------------------------------------------------------
>
> 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
> Assignee: Harsh J
> Labels: io, serialization
> Fix For: 0.23.0
>
> Attachments: 0.22-HADOOP-7328.r7.diff, 0.23-HADOOP-7328.r7.diff,
> HADOOP-7328.r1.diff, HADOOP-7328.r2.diff, HADOOP-7328.r3.diff,
> HADOOP-7328.r4.diff, HADOOP-7328.r4.diff, HADOOP-7328.r5.diff,
> HADOOP-7328.r6.diff, HADOOP-7328.r7.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
