As a general point, if you want an MR property to apply to the launcher job, you can prefix any MR property with "oozie.launcher.*". If you want an MR property to apply to the actual job, you just specify it normally.
- Robert On Thu, Sep 19, 2013 at 5:42 AM, Giridhar Addepalli <[email protected]>wrote: > Thanks for the idea Badri Narayanan. > > "oozie.launcher.firstname" property under 'configuration' tag in > workflow.xml worked. > > Thanks, > Giridhar. > > > On Thu, Sep 19, 2013 at 4:51 PM, Badri Narayanan <[email protected]> > wrote: > > > Can you prefix the property with "mapred.job" in your oozie xml? For eg., > > "mapred.job.firstname", "Giridhar". > > > > > > On Thu, Sep 19, 2013 at 4:22 PM, Giridhar Addepalli > > <[email protected]>wrote: > > > > > Hi, > > > > > > I am trying to add some arbitrary parameter to jobconf , i.e; all the > MR > > > jobs started by oozie actions should have that parameter in their > > JobConf. > > > > > > I tried using below two approaches > > > 1) oozieClient.createConfiguration().setProperty("firstname", > "Giridhar") > > > 2) on the command line -D firstname=Giridhar > > > > > > I could see this property in the xml when i clicked on "Job > > Configuration" > > > tab on the oozie web console. > > > But i could not see this property in the JobConf of the MR job > started. > > ( > > > i.e; when i clicked on link in the Console Url ). > > > > > > Any suggestions. > > > > > > Thanks, > > > Giridhar. > > > > > >
