You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by Dhruba Borthakur <dh...@gmail.com> on 2008/12/30 20:08:38 UTC

Deprecate JobClient.getCommandLineConfig?

The method JobClient.getCommandLineConfig and JobClient.setCommandLineOption
were public APIs but seem to have disappeared starting from the 0.20
release. Is this on purpose? If so, what is the alternative method to
retrieve the job's conf?

thanks
dhruba

Re: Deprecate JobClient.getCommandLineConfig?

Posted by Amareshwari Sriramadasu <am...@yahoo-inc.com>.

Dhruba Borthakur wrote:
> The method JobClient.getCommandLineConfig and JobClient.setCommandLineOption
> were public APIs but seem to have disappeared starting from the 0.20
> release. Is this on purpose? If so, what is the alternative method to
> retrieve the job's conf?
>
> thanks
> dhruba
>
>   
Hi Dhruba,

Yes. It is done on purpose through HADOOP-3986. The configuration is 
static configuration in JobClient,  it is not the Job Configuration. It 
was used  to  parse  -libjars, -files and -archives options only, if the 
application does not implement Tool as they are part of GenericOptions.

Where do you to want access the Job configuration? If it is in map() or 
reduce(), you should use configure() method.

Thanks
Amareshwari