[
https://issues.apache.org/jira/browse/HADOOP-10898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15634094#comment-15634094
]
Eli Acherkan edited comment on HADOOP-10898 at 11/3/16 8:12 PM:
----------------------------------------------------------------
Thanks [~ViniciusMSAna], it definitely looks like the same issue. I'd love to
help there (and I think the patch I attached should solve the problem), but I'm
a bit unfamiliar with the process - could you tell me what should I do?.. The
last comment on that issue says "Marking it "Unassgined" in case someone else
wants to take a stab it. Will reclaim if it is still open by the time I get to
it."
was (Author: eliac):
Thanks @VinciusMSAna, it definitely looks like the same issue. I'd love to help
there (and I think the patch I attached should solve the problem), but I'm a
bit unfamiliar with the process - could you tell me what should I do?.. The
last comment on that issue says "Marking it "Unassgined" in case someone else
wants to take a stab it. Will reclaim if it is still open by the time I get to
it."
> MapWritable instances cannot be reused when containing different custom
> Writable classes.
> -----------------------------------------------------------------------------------------
>
> Key: HADOOP-10898
> URL: https://issues.apache.org/jira/browse/HADOOP-10898
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Reporter: Eli Acherkan
> Priority: Minor
> Attachments: HADOOP-10898.patch
>
>
> When a data stream contains several MapWritable instances, which contain
> instances of several different custom classes (implementing Writable),
> attempting to reuse a single MapWritable instance for reading the data stream
> results in an IllegalArgumentException. This happens because
> AbstractMapWritable.readFields doesn't reset the classToIdMap/idToClassMap
> data structures.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
