I think I've found the problem. When I removed the following line:
conf.setCombinerClass(Reduce.class);
everything worked fine. During the map phase, when the combiner uses the
Reduce.class as the Reducer, the final map (key,value) pairs are attempted
to be written as the Reducer output types, which contradict with the
specified Mapper output types. If I'm correct, am I supposed to write a
separate reducer for the local combiner in order to speed things up?
Jim
On Fri, Aug 29, 2008 at 6:30 PM, Jim Twensky <[EMAIL PROTECTED]> wrote:
> Here is the relevant part of my mapper:
>
> (...)
>
> private final static IntWritable one = new IntWritable(1);
> private IntWritable bound = new IntWritable();
>
> (...)
>
> while(...) {
>
> output.collect(bound,one);
>
> }
>
> so I'm not sure why my mapper tries to output a FloatWritable.
>
>
>
>
> On Fri, Aug 29, 2008 at 6:17 PM, Owen O'Malley <[EMAIL PROTECTED]> wrote:
>
>> The error message is saying that your map tried to output a FloatWritable.
>>
>
>
