[
https://issues.apache.org/jira/browse/FLINK-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289427#comment-14289427
]
Ufuk Celebi commented on FLINK-1427:
------------------------------------
You could easily check whether the variable is already set and print a warning.
It's just a matter of what we want to give precedence to.
I agree that it is error prone to configure the same thing in different places
(although I think that Alexander was referring to something else).
Since no user really complained so far, we should stick to your non intrusive
proposal and essentially keep everything as is.
> Configuration through environment variables
> -------------------------------------------
>
> Key: FLINK-1427
> URL: https://issues.apache.org/jira/browse/FLINK-1427
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Environment: Deployment
> Reporter: Max Michels
> Priority: Minor
> Labels: configuration, deployment
>
> Like Hadoop or Spark, etc. Flink should support configuration via shell
> environment variables. In cluster setups, this makes things a lot easier
> because writing config files can be omitted. Many automation tools (e.g.
> Google's bdutil) use (or abuse) this feature.
> For example, to set up the task manager heap size, we would run `export
> FLINK_TASKMANAGER_HEAP=4096` before starting the task manager on a node to
> set the heap memory size to 4096MB.
> Environment variables should overwrite the regular config entries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
