[ https://issues.apache.org/jira/browse/FLINK-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger resolved FLINK-2954. ----------------------------------- Resolution: Fixed Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/b9639eb5 > 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)