hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-680) Reuse of Writable objects is improperly handled by MRUnit
Date Fri, 17 Jul 2009 16:56:15 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12732603#action_12732603

Hudson commented on MAPREDUCE-680:

Integrated in Hadoop-Mapreduce-trunk #25 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Mapreduce-trunk/25/])

> Reuse of Writable objects is improperly handled by MRUnit
> ---------------------------------------------------------
>                 Key: MAPREDUCE-680
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-680
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Aaron Kimball
>            Assignee: Aaron Kimball
>             Fix For: 0.21.0
>         Attachments: MAPREDUCE-680.patch
> As written, MRUnit's MockOutputCollector simply stores references to the objects passed
in to its collect() method. Thus if the same Text (or other Writable) object is reused as
an output containiner multiple times with different values, these separate values will not
all be collected. MockOutputCollector needs to properly use io.serializations to deep copy
the objects sent in.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message