Thanks Robert, Serega. I am able to override the precedence using the launcher property as per OOZIE-2066.
Som On Thu, Feb 12, 2015 at 10:01 AM, Robert Kanter <[email protected]> wrote: > I think you're misunderstanding how this works. Any "oozie.launcher.*" and > Hadoop (i.e. "mapreduce.*") properties go in the <configuration> section of > the action, not the job.properties (or in the case of OOZIE-2066, > hello-world.xml). This is behaving as expected. > > - Robert > > On Thu, Feb 12, 2015 at 12:19 AM, Serega Sheypak <[email protected] > > > wrote: > > > What do you try to solve? > > oozie.launcher.mapreduce.task.classpath.user.precedence used for > > oozie-action > > > > mapreduce.task.classpath.user.precedence used for MR job > > > > 2015-02-12 6:39 GMT+03:00 Som Satpathy <[email protected]>: > > > > > Has any one been able to successfully apply the > > > 'oozie.launcher.mapreduce.task.classpath.user.precedence' in their > oozie > > > workflows? > > > > > > Reference - https://issues.apache.org/jira/browse/OOZIE-2066 > > > > > > I have CDH5.3.1 set up running oozie 4.0.0. No success for me. > > > > > > Thanks, > > > Som > > > > > >
