mrunit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dave Beech <>
Subject Re: TestDriver
Date Thu, 22 Nov 2012 14:36:01 GMT
Probably. There are other issues like this, for
example setKeyGroupingComparator and setKeyOrderComparator on
MapReduceDriverBase create an instance of the comparator straight away,
using whatever conf is currently available.

If the user decides to provide a different config later which contains
settings that would have been used when creating the comparators, well ....
unlucky. I mentioned this on one of the issues in JIRA but can't remember
right now which one it was.

If possible I think we should defer creation of these objects until right
before the test starts running.


On 22 November 2012 14:24, Brock Noland <> wrote:

> In TestDriver:
>     configuration = new Configuration();
>     serialization = new Serialization(configuration);
> in the constructor but then we allow people to set the configuration
> object without re-creating the Serialization object. Is this
> problematic?  I am looking at MRUNIT-161 which will require the
> configuration object as well, but down in the Mock*Context classes.
> Brock
> --
> Apache MRUnit - Unit testing MapReduce -

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message