Re: Command-line jobConf options in 0.18.3

2009-06-04 Thread Raghu Angadi
Tom White wrote: Actually, the space is needed, to be interpreted as a Hadoop option by ToolRunner. Without the space it sets a Java system property, which Hadoop will not automatically pick up. I don't think space is required. Something like -Dfs.default.name=host:port works. I don't see Tool

Re: Command-line jobConf options in 0.18.3

2009-06-04 Thread Tom White
Actually, the space is needed, to be interpreted as a Hadoop option by ToolRunner. Without the space it sets a Java system property, which Hadoop will not automatically pick up. Ian, try putting the options after the classname and see if that helps. Otherwise, it would be useful to see a snippet o

Re: Command-line jobConf options in 0.18.3

2009-06-04 Thread Vasyl Keretsman
Perhaps, there should not be the "space" between -D and your option ? -Dprise.collopts= Vasyl 2009/6/4 Ian Soboroff : > > bin/hadoop jar -files collopts -D prise.collopts=collopts p3l-3.5.jar > gov.nist.nlpir.prise.mapred.MapReduceIndexer input output > > The 'prise.collopts' option doesn

Re: Command-line jobConf options in 0.18.3

2009-06-04 Thread Ian Soboroff
bin/hadoop jar -files collopts -D prise.collopts=collopts p3l-3.5.jar gov.nist.nlpir.prise.mapred.MapReduceIndexer input output The 'prise.collopts' option doesn't appear in the JobConf. Ian Aaron Kimball writes: > Can you give an example of the exact arguments you're sending on the command

Re: Command-line jobConf options in 0.18.3

2009-06-04 Thread Aaron Kimball
Can you give an example of the exact arguments you're sending on the command line? - Aaron On Wed, Jun 3, 2009 at 5:46 PM, Ian Soboroff wrote: > If after I call getConf to get the conf object, I manually add the > key/value pair, it's there when I need it. So it feels like ToolRunner > isn't pa

Re: Command-line jobConf options in 0.18.3

2009-06-03 Thread Ian Soboroff
If after I call getConf to get the conf object, I manually add the key/ value pair, it's there when I need it. So it feels like ToolRunner isn't parsing my args for some reason. Ian On Jun 3, 2009, at 8:45 PM, Ian Soboroff wrote: Yes, and I get the JobConf via 'JobConf job = new JobConf(con

Re: Command-line jobConf options in 0.18.3

2009-06-03 Thread Ian Soboroff
Yes, and I get the JobConf via 'JobConf job = new JobConf(conf, the.class)'. The conf is the Configuration object that comes from getConf. Pretty much copied from the WordCount example (which this program used to be a long while back...) thanks, Ian On Jun 3, 2009, at 7:09 PM, Aaron Kimb

Re: Command-line jobConf options in 0.18.3

2009-06-03 Thread Aaron Kimball
Are you running your program via ToolRunner.run()? How do you instantiate the JobConf object? - Aaron On Wed, Jun 3, 2009 at 10:19 AM, Ian Soboroff wrote: > I'm backporting some code I wrote for 0.19.1 to 0.18.3 (long story), and > I'm finding that when I run a job and try to pass options with -

Command-line jobConf options in 0.18.3

2009-06-03 Thread Ian Soboroff
I'm backporting some code I wrote for 0.19.1 to 0.18.3 (long story), and I'm finding that when I run a job and try to pass options with -D on the command line, that the option values aren't showing up in my JobConf. I logged all the key/value pairs in the JobConf, and the option I passed t