[OOZIE-2687] Create XML schema for launcher configurations

• Type: Sub-task
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 5.0.0
• Fix Version/s: 5.0.0b1
• Assignee: Attila Sasvári
• Reporter: Gézapeti
• Created: 26/Sep/16 12:19
• Updated: 25/Jan/18 21:00
• Resolved: 18/Sep/17 11:00

Description

It was possible to manipulate the MapperLauncher's environment through properties like:

1. mapreduce.map.memory.mb
2. mapreduce.map.cpu.vcores
3. mapred.child.env
4. mapred.child.java.opts
5. 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.

Issue Links

• blocks: OOZIE-2814 OYA: Update example workflows to newest schemas
• is depended upon by: OOZIE-3056 Implement new mechanism to specify ShareLibs for workflow actions
• relates to: OOZIE-3033 Extract workflow action XML schemas to separate xsd-s
• relates to: OOZIE-3034 Allow setting default core/memory/queue for launcher per action type
• links to: ReviewBoard