You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Johannes (JIRA)" <ji...@apache.org> on 2013/06/27 20:05:22 UTC
[jira] [Commented] (HADOOP-7239) The variables in the configuration
files are not replaced with values, when the job is submitted by Job client
[ https://issues.apache.org/jira/browse/HADOOP-7239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694929#comment-13694929 ]
Johannes commented on HADOOP-7239:
----------------------------------
This seems to be an issue with the current version, too.
> The variables in the configuration files are not replaced with values, when the job is submitted by Job client
> --------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7239
> URL: https://issues.apache.org/jira/browse/HADOOP-7239
> Project: Hadoop Common
> Issue Type: Bug
> Components: conf
> Affects Versions: 0.20.2, 0.21.0
> Environment: Linux + Sun JDK 1.6
> Reporter: Venu Gopala Rao
>
> We have a case where we wanted to create the Job names dynamically at run time.Since JobConf is an extension for the Configuration object, we thought we can make use of the variable substitution concept in configuration like below
> Job job = new Job(conf, "${mapred.user.name}" + "-job" + new Random().nextInt());
> job.setJarByClass(WordCount.class);
> job.setMapperClass(TokenizerMapper.class);
> job.setCombinerClass(IntSumReducer.class);
> job.setReducerClass(IntSumReducer.class);
> job.setOutputKeyClass(Text.class);
> job.setOutputValueClass(IntWritable.class);
> FileInputFormat.addInputPath(job, new Path(otherArgs[0]));
> FileOutputFormat.setOutputPath(job, new Path(otherArgs[1]));
> job.submit();
> We set the required run time variables(in this case mapred.user.name) before calling the job submit. But on the Job tracker side the variables are not replaced correctly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira