I'm pretty new to this stuff, too, but I can't see why the current use of the combiner is a problem. The combiner class is basically there as an option to reduce the amount of intermediate output that gets written into NDFS before the reduce is started - there's no reason to call it from the reducer too. Generally, it probably even does the same logic - I've been building testing scenarios that work exactly that way, using the same class for reduce as combine.
On 1/29/06, Stefan Groschupf <[EMAIL PROTECTED]> wrote: > > Hi, > just to add this to the archive. I note that the combiner class as it > is settedin the regex demo, is never used in the reducer task. > Also only the mapper task tests if there is a combiner class setted > to use the combining collector for map tasks. > > So we may can remove getter and setter for combinder class in the job > Conf or should add the usage of the combiner class.:) > > Stefan > -- Bryan A. Pendleton Ph: (877) geek-1-bp
