[
https://issues.apache.org/jira/browse/HADOOP-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354243#comment-14354243
]
Hadoop QA commented on HADOOP-7021:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12503833/HADOOP-7021.patch
against trunk revision 82db334.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5899//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/5899//console
This message is automatically generated.
> 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)
