hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Kimball <aa...@cloudera.com>
Subject Re: Command-line jobConf options in 0.18.3
Date Thu, 04 Jun 2009 08:11:24 GMT
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 <ian.soboroff@nist.gov> 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 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(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 Kimball wrote:
>>
>>  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 <ian.soboroff@nist.gov>
>>> 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 -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
>>> through with -D isn't there.
>>>
>>> This worked in 0.19.1... did something change with command-line options
>>> from 18 to 19?
>>>
>>> Thanks,
>>> Ian
>>>
>>>
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message