[
https://issues.apache.org/jira/browse/HADOOP-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12928615#action_12928615
]
Hadoop QA commented on HADOOP-7021:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12458910/AbstractMapWritable.java
against trunk revision 1031422.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/57//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
> Environment: Hadoop 0.20.1, Centos
> Reporter: John Lee
> Priority: Minor
> Fix For: 0.20.1
>
> Attachments: AbstractMapWritable.diff, AbstractMapWritable.java,
> TestMapWritableNPE.java
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
