I agree.
But in general we can remove the possibility to configure combiner
classes in the jobconf in case custom combiner classes are never used.
It is just about cleaning up the API.
Stefan
Am 30.01.2006 um 20:51 schrieb Bryan A. Pendleton:
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
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Nutch-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nutch-developers
