[
https://issues.apache.org/jira/browse/FLINK-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285744#comment-14285744
]
Alexander Alexandrov commented on FLINK-1427:
---------------------------------------------
I am not too fond of this idea.
I like having one clean entry point to the configuration of the system and a
clear section documenting how I can change that configuration. One of the main
issues I always have when dealing with Spark / Hadoop is deciding where and how
to configure what.
We actually had an environment based approach in the project in past, but
removed it in order to simplify the configuration options and have them all in
one place.
I suggest to think again about this one, as it will also require at least
(1) making sure that the documentation explains that there are multiple
equivalent setup options;
(2) ensure that these setup options are actually equivalent.
> 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)
