Sorry, meant to say fs.default.name for the namenode property. On Nov 8, 2011 1:32 PM, "Jamal B" <[email protected]> wrote:
> Thanks for the response it helped. > > I fixed the problem by adding a core-site.xml file to the root of my jar, > and added the fs.name.dir and mapred.job.tracker properties to it and it > worked. > On Nov 8, 2011 9:24 AM, "Sean Owen" <[email protected]> wrote: > >> This is more a Hadoop question; I don't think it's finding your config >> files. I think the Configuration object has methods that let you >> specify which config to read and you should use these to make sure >> it's finding the Hadoop config. >> >> On Tue, Nov 8, 2011 at 2:09 PM, Jamal B <[email protected]> wrote: >> > Good morning, >> > >> > Would it be possible for anyone to point me in the right direction with >> a >> > minor problem I am having. I'm trying to run a job using the >> > BayesFeatureDriver (version 0.5) from my webapp which would use a >> remote >> > hadoop cluster. The problem I am having is that the driver executes >> > assuming a local hadoop instance instead of the remote cluster. I have >> a >> > copy of my cluster's conf/core-site.xml & core/mapred-site.xml files in >> my >> > jar containing the driver and supporting code. However, it appears that >> > they are not being used by the BayesFeatureDriver.runJob() invocation. >> Is >> > there another piece of setup that I am missing? >> > >> > Thanks for any help. >> > >> >
