Robert Young wrote:
In org.apache.nutch.crawl.LinkDb on line 261 it creates a working
directory (newLinkDb) based on the current working directory. This
should be configurable rather than being based on where Tomcat was
started. I am planning on writing a patch to pull the hadoop.tmp.dir
Tomcat only comes into it because we have to start Tomcat in the
searcher directory, I'm guessing it's the same however you choose to
use Nutch. It would still have to do a rename across physical volumes
if searcher.dir is set to something different would it not?
How does this sound as a
I don't use the nutch web application, but You don't have to
start nutch in the searcher directory. You can set the location of
the searcher dir within the nutch-site.xml config file.
Add this node and set the location of your index:
property
namesearcher.dir/name
Yes, I do this for the searcher directory but in the LinkDb class it
makes a reference to a Path which is relative (just for a temporary
working directory). This is the problem, because if I start tomcat in
a path where the java user does not have permissions to create a
directory then LinkDb
Ahh, now I see what you are referring to. Thanks for the question.
Now I know why I was getting garbage in my directory a while back.
So, I guess you may need to edit that class. Are you using hadoop in
local mode?
On 7/19/07, Robert Young [EMAIL PROTECTED] wrote:
Yes, I do this for the
