> I'm correct that this can be used to modify other fetcher attributes too? > (I like DataParkSearch's abilities to essentially make almost everything > making sense per domain - tuneable) >
yes - you could apply the same logic to other aspects of the fetching and define reserved feature names for doing so > Is it correct that 2.0 will have only solr-indexer(and not 'regular' > searcher)? > What about search webinterface(currently what I see on solr is API for > _making_ one,not basic interface like regular nutch one) > the features of Nutch 2.0 are still under discussion but you are basically correct - the plan is to delegate the indexing and search to SOLR and get rid of the Lucene and search components in Nutch. This includes the search servers and front ends IMHO. I think there are quite a few front ends available for SOLR but better to ask on their list. J. > > HTH > > > > Julien > > > > -- > > DigitalPebble Ltd > > > > Open Source Solutions for Text Engineering > > http://www.digitalpebble.com > > > > On 23 June 2010 11:36, Dmitriy V. Kazimirov > > <[email protected]>wrote: > > > > > Hi, > > > > > > Is it possible (likely not but still) to make Nutch use different > > values > > > of fetcher.threads.per.host for different domains? > > > > > > i.e. low default value(1-3) and for domains which I _knew_ can handle > > load > > > and it won't be problem - increase it > > > > > > > > > > > > If that's not possible could someone give advice where in code to > > look to > > > make such modifications? > > > > > > > > > > > > > > > > > > With regards, Dmitriy Kazimirov > > > > > > > -- DigitalPebble Ltd Open Source Solutions for Text Engineering http://www.digitalpebble.com
