[
https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543072#comment-15543072
]
Peter Cseh commented on OOZIE-2687:
-----------------------------------
We could add the most commonly set properties e.g. launcher memory or launcher
vcores into the schema instead of using properties for those.
We could introduce a <launcher-memory> or <launcher-vcores> tag or a <launcher>
tag with <memory>, <vcores>, <env> and <java-opts> in it.
We should decide which are the most commonly used properties and make sure we
support most of them to make the upgrade easy for the users.
> 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
>
> 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
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
