[jira] [Commented] (OOZIE-2687) OYA: Figure out how to handle MR-specific properties

["Robert Kanter (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901773#comment-15901773 ] 

Robert Kanter commented on OOZIE-2687:
--------------------------------------

FYI: I've just filed OOZIE-2814 to update the examples with the newest schemas after this JIRA is done.  Besides using really old schemas in most examples, it would be a good way to show off the new schema changes.

> OYA: Figure out how to handle MR-specific properties
> ----------------------------------------------------
>
>                 Key: OOZIE-2687
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2687
>             Project: Oozie
>          Issue Type: Sub-task
>            Reporter: Peter Cseh
>            Assignee: Peter Bacsko
>
> 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.3.15#6346)