[
https://issues.apache.org/jira/browse/OOZIE-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15705122#comment-15705122
]
Peter Cseh commented on OOZIE-2687:
-----------------------------------
I like the idea of being compatible with Hadoop.
However, I don't like the idea of using an OS-dependent separator:
|mapred.child.env| User added environment variables for the task
tracker child processes. Example : 1) A=foo This will set the env variable A to
foo 2) B=$B:c This is inherit nodemanager's B env variable on Unix. 3) B=%B%;c
This is inherit nodemanager's B env variable on Windows.|
|mapreduce.admin.user.env| Expert: Additional execution
environment entries for map and reduce task processes. This is not an additive
property. You must preserve the original value if you want your map and reduce
tasks to have access to native libraries (compression, etc). When this value is
empty, the command to set execution envrionment will be OS dependent: For
linux, use LD_LIBRARY_PATH=$HADOOP_COMMON_HOME/lib/native. For windows, use
PATH = %PATH%;%HADOOP_COMMON_HOME%\\bin.|
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
