[
https://issues.apache.org/jira/browse/HADOOP-7021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14535022#comment-14535022
]
Hadoop QA commented on HADOOP-7021:
-----------------------------------
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch | 0m 0s | The patch command could not apply
the patch during dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12503833/HADOOP-7021.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f0f5e3c |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/6545/console |
This message was 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
> Labels: BB2015-05-RFC
> 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)
