On 08/11/2010 08:14 PM, Aaron Kimball wrote:
David,
Since you are directly instantiating the Mapper and Reducer (not using
ReflectionUtils), you are free to call setConf() yourself before you run the
test.
Sort of. What would wind up happening is that setConf would get called
twice: once by
David,
Since you are directly instantiating the Mapper and Reducer (not using
ReflectionUtils), you are free to call setConf() yourself before you run the
test.
If you're using the old API (o.a.h.mrunit):
Mapper m = new Mapper();
MapDriver d = new MapDriver(m);
Configuration conf = new Configura
On 08/10/2010 04:54 PM, David Rosenstrauch wrote:
On 08/10/2010 04:24 PM, David Rosenstrauch wrote:
What I'm looking for is a way to initialize the reducer using a
particular Configuration object, which contains the parms/properties
that the reducer needs. I looked at the ReduceDriver class, how
On 08/10/2010 04:24 PM, David Rosenstrauch wrote:
What I'm looking for is a way to initialize the reducer using a
particular Configuration object, which contains the parms/properties
that the reducer needs. I looked at the ReduceDriver class, however, and
there doesn't seem to be any way to do th
I'm trying to write some tests with the mrunit framework, but running
into a snag.
It seems that the mock Context objects that are being created are always
using a new, empty Configuration object. However, I've written my
reducer to implement Configurable, since in production I'm going to be
