[
https://issues.apache.org/jira/browse/HADOOP-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085227#comment-13085227
]
Hadoop QA commented on HADOOP-7021:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12490322/HADOOP-7021.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these core unit tests:
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/37//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/37//artifact/trunk/target/newPatchFindbugsWarningshadoop-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HADOOP-Build/37//artifact/trunk/target/newPatchFindbugsWarningshadoop-annotations.html
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/37//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
> Priority: Minor
> Fix For: 0.20.1
>
> Attachments: 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
