[ https://issues.apache.org/jira/browse/OOZIE-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shwetha G S updated OOZIE-1696: ------------------------------- Fix Version/s: (was: trunk) 4.2 > Document how to get the action conf in the Java action > ------------------------------------------------------ > > Key: OOZIE-1696 > URL: https://issues.apache.org/jira/browse/OOZIE-1696 > Project: Oozie > Issue Type: Sub-task > Components: docs > Affects Versions: trunk > Reporter: Robert Kanter > Assignee: James Kinley > Labels: newbie > Fix For: 4.2 > > Attachments: OOZIE-1696.patch > > > The Java action doesn't get a lot of the "magic" that we do in the other > actions, so things don't always behave right for users using the Java action > to launch MapReduce jobs. We've seen some confusion where these jobs were > picking up the mapred-default properties and not working because of it. It > would be great if we could document how to use the job conf prepared by > Oozie, which includes the proper mapred-site.xml (and other site files), plus > anything in the {{<configuration>}} section of the Java action. > Basically, they just need to create their job conf with something like this > (taken from MapReduceMain.java): > {code:java} > Configuration actionConf = new Configuration(false); > actionConf.addResource(new Path("file:///", > System.getProperty("oozie.action.conf.xml"))); > {code} > We can put it next to the already documented snippet about the delegation > token propagation here: > http://oozie.apache.org/docs/4.0.0/WorkflowFunctionalSpec.html#a3.2.7_Java_Action -- This message was sent by Atlassian JIRA (v6.3.4#6332)