[
https://issues.apache.org/jira/browse/MRUNIT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13658761#comment-13658761
]
Brock Noland commented on MRUNIT-187:
-------------------------------------
Hi [~jnovak],
We made the drivers non-reusable in MRUNIT-138, but it appears we didn't use
some internal flag to throw an assertion error if run() is called twice.
Perhaps we should do that in this issue.
Brock
> previous outputs not cleared by ReduceDriver.run()
> --------------------------------------------------
>
> Key: MRUNIT-187
> URL: https://issues.apache.org/jira/browse/MRUNIT-187
> Project: MRUnit
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Jason Novak
>
> I have a unit test that reuses the same ReduceDriver with 2 different sets of
> inputs. With 1.0.0, the second call to reduceDriver.run() returns the first
> run's outputs as well as the second's. This is a regression since
> 0.9.0-incubating.
> Pseudocode:
> // called twice
> reduceDriver.setInputKey(key);
> for (int i = 0; i < 5 ; ++i) {
> reduceDriver.addInputValue(v);
> }
> List<Pair<K, V>> outputs = reduceDriver.run();
--
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
