[
https://issues.apache.org/jira/browse/MRUNIT-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13580128#comment-13580128
]
David Parks commented on MRUNIT-13:
-----------------------------------
Found a problem in what I did, I had created a mock of the Reducer class, but
this was both buggy and distasteful. Buggy because the mock nulled out other
fields in the mock Reducer class (oops, newbie mistake), and just distasteful
because I had to create a new copy of the object, so if the user had made some
settings to the class after creating it we might have silently discarded them.
I swapped out mock() for spy() and it seems to behave better now (spy uses the
same reduce object the user created). I still haven't implemented all the
methods yet, and still need to test it more before I'm confident in the
approach, but just wanted to post the tweak. If someone's interested I'll post
the update (just a 2-line change).
> Add support for MultipleOutputs
> -------------------------------
>
> Key: MRUNIT-13
> URL: https://issues.apache.org/jira/browse/MRUNIT-13
> Project: MRUnit
> Issue Type: New Feature
> Reporter: E. Sammer
> Assignee: Jim Donofrio
> Attachments: mapreduce.zip
>
>
> Add support to mrunit for Hadoop's MultipleOutputs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
