You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2015/03/10 03:52:38 UTC
[jira] [Updated] (HADOOP-7021) MapWritable NullPointerException
[ https://issues.apache.org/jira/browse/HADOOP-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer updated HADOOP-7021:
-------------------------------------
Fix Version/s: (was: 0.20.1)
> MapWritable NullPointerException
> --------------------------------
>
> Key: HADOOP-7021
> URL: https://issues.apache.org/jira/browse/HADOOP-7021
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Affects Versions: 0.20.1, 0.21.0
> Environment: Hadoop 0.20.1, Centos
> Reporter: John Lee
> Assignee: John Lee
> Priority: Minor
> Attachments: HADOOP-7021.patch, HADOOP-7021.patch, HADOOP-7021.patch, HADOOP-7021.patch
>
>
> We have encountered a NullPointerException when we use MapWritable with custom Writable objects.
> The root cause is the counter newClasses in AbstractMapWritable is allowed to get out of sync with the id to class mapping tables when addToMap(Class) is called. We have a patch to AbstractMapWritable.addToMap(Class) that handles the case when newClasses gets out of sync with the id to class mapping tables and adds a serialization optimization to minimize the number of class names to write out per MapWritable object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)