[ https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Sasvari updated OOZIE-2687: ---------------------------------- Attachment: OOZIE-2687-001.patch I had to make some modifications in [~pbacsko] wip Tested - TestJavaActionExecutor, TestLiteWorkflowAppParser tests passed - java-main example on pseudo hadoop succeeded, modified workflow xml so that verbose class loading information is printed out of stdout of the launcher job {code} <workflow-app xmlns="uri:oozie:workflow:0.6" name="java-main-wf"> <start to="java-node"/> <action name="java-node"> <java> <job-tracker>${jobTracker}</job-tracker> <name-node>${nameNode}</name-node> <launcher> <java-opts>-verbose:class</java-opts> </launcher> <configuration> <property> <name>mapred.job.queue.name</name> <value>${queueName}</value> </property> </configuration> <main-class>org.apache.oozie.example.DemoJavaMain</main-class> <arg>Hello</arg> <arg>Oozie!</arg> </java> <ok to="end"/> <error to="fail"/> </action> <kill name="fail"> <message>Java failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message> </kill> <end name="end"/> </workflow-app> {code} Logs: {code} head -3 /Users/asasvari/workspace/pseudo/hadoop-2.6.0/logs/userlogs/application_1502291380639_0001/container_1502291380639_0001_01_000001/stdout [Opened /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/rt.jar] [Loaded java.lang.Object from /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/rt.jar] [Loaded java.io.Serializable from /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/rt.jar] {code} > Create XML schema for launcher configurations > --------------------------------------------- > > Key: OOZIE-2687 > URL: https://issues.apache.org/jira/browse/OOZIE-2687 > Project: Oozie > Issue Type: Sub-task > Reporter: Peter Cseh > Assignee: Peter Bacsko > Attachments: OOZIE-2687-001.patch > > > It was possible to manipulate the MapperLauncher's environment through > properties like: > # mapreduce.map.memory.mb > # mapreduce.map.cpu.vcores > # mapred.child.env > # mapred.child.java.opts > # mapred.job.queue.name - ability to set launcher queue > E.g. We were using mapred.child.env to pass SPARK_HOME to the LauncherMapper > and make PySpark work. > Fixing OOZIE-2596 added a hack. We should decide how we support or break > compatibility and how we allow the manipulation of the Launcher environment. > Verify if the new launcher section in global applies to actions in > sub-workflows as well. It did not use to work before and was only fixed in > OOZIE-2030. It would be good to have that testcase > (TestSubWorkflowActionExecutor. testParentGlobalConf) updated with the new > launcher section as well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)