Hi Andrzej,
thanks a lot!!
Stefan
On 08.07.2005, at 17:45, Andrzej Bialecki (JIRA) wrote:
[ http://issues.apache.org/jira/browse/NUTCH-63?page=all ]
Andrzej Bialecki closed NUTCH-63:
--
Resolution: Fixed
Changed to LOG.finest().
the distributed se
[ http://issues.apache.org/jira/browse/NUTCH-63?page=all ]
Andrzej Bialecki closed NUTCH-63:
--
Resolution: Fixed
Changed to LOG.finest().
> the distributed search client generate too much logging statements
> --
[ http://issues.apache.org/jira/browse/NUTCH-69?page=all ]
Andrzej Bialecki resolved NUTCH-69:
Resolution: Invalid
This behaviour is caused by improper configuration. When crawling less hosts
than (fetcher threads / threads per host), some thr
fetcher.threads.per.host ignored
Key: NUTCH-69
URL: http://issues.apache.org/jira/browse/NUTCH-69
Project: Nutch
Type: Bug
Components: fetcher
Reporter: Matthias Jaekle
Fetcher ignores 'maximum threads per host'.
If you fetc
can anyone e-mail me a compiled version of the nutch-nightly.jar with this
fix please?
Thanks
-Jay Pound
[EMAIL PROTECTED]
---
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite
Hi everybody,
I have some performance problems running nutch. My scenario: I build a
nutch system with
- about 5 mio indexed (!) documents (measured by luke and over the web)
- segread returns about 10 mio known documents
- there are 58 segments (making about 90.000 indexed documents per
segme
[ http://issues.apache.org/jira/browse/NUTCH-58?page=all ]
Andrzej Bialecki closed NUTCH-58:
--
Resolution: Fixed
Applied. Thanks!
> NullPointerException while coping NDFS file
>
>
> Key: NUTCH
