[jira] [Resolved] (MRUNIT-187) previous outputs not cleared by ReduceDriver.run()

["Brock Noland (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MRUNIT-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brock Noland resolved MRUNIT-187.
---------------------------------

    Resolution: Won't Fix

Marking as won't fix and taking the issue forward in MRUNIT-188.
                
> 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