Dear Aaron,
Thanks for your reply!
It's very help for you to tell me this, I don't know that the key type of
the final output also can be different from the intermediate result.
That's great!
Best Regards
Jiamin Lu
Glad you figured out your bug. It's worth pointing out that Google's
MapReduce has stricter type signatures than Hadoop does. Hadoop allows the
final (k, v) pairs to be of a different type than the inputs to the reducer,
and the final key associated with a final value does not necessarily need to
b
Hi, all
I solved it!
By through set:
conf.setMapOutputKeyClass(Text.class);
conf.setMapOutputValueClass(BytesWritable.class);
conf.setOutputKeyClass(Text.class);
conf.setOutputValueClass(Text.class);
So stupid I am! I need to read more documents first!
Best Regar
Hi, all
>From the original paper of mapReduce by google, the signature of data
transform is that:
map: (k1, v1) -> list(k2, v2)
reduce: (k2, list(v2)) -> list(v2)
Here, the output value type is v2, and the final type is also v2.
But, what I want to achieve is that, the final value type should
