[
https://issues.apache.org/jira/browse/FLINK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028592#comment-15028592
]
ASF GitHub Bot commented on FLINK-2954:
---------------------------------------
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/1409
[FLINK-2954] Add config parameter for passing environment variables to YARN
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/flink flink2954
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1409.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1409
----
commit 74044d75b931b217f33816a7c9ed6f2ab085cb07
Author: Robert Metzger <[email protected]>
Date: 2015-11-26T10:47:25Z
[FLINK-2954] Add config parameter for passing environment variables to YARN
----
> Not able to pass custom environment variables in cluster to processes that
> spawning TaskManager
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-2954
> URL: https://issues.apache.org/jira/browse/FLINK-2954
> Project: Flink
> Issue Type: Bug
> Components: Command-line client, Distributed Runtime
> Affects Versions: 0.10.0
> Reporter: Jian Jiang
> Assignee: Robert Metzger
> Priority: Critical
> Fix For: 1.0.0
>
>
> There are programs that rely on custom environment variables. In hadoop
> mapreduce job we can use -Dmapreduce.map.env and - Dmapreduce.reduce.env to
> do pass them. Similarly in Spark
> we can use --conf 'spark.executor.XXX=value for XXX'. There is no such
> feature yet in Flink.
> This has given Flink a serious disadvantage when customers need such feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
