[
https://issues.apache.org/jira/browse/FLINK-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137249#comment-16137249
]
Jamie Grier commented on FLINK-4947:
------------------------------------
[~gaborhermann] It's more than just that but yes I do suggest that you should
be able to override what's in the config file on the command line.
More importantly though is that all *config* should be configurable via
flink-conf.yaml. We shouldn't add features that are only configurable from the
*user code*.
An example of this used to be the RocksDB state backend. If you wanted to use
that backend and configure it in "async" mode you had to put this in
application code, but that's not great for separation of concerns between
application developers and ops/platform teams.
I know this isn't black-and-white but we should try to clearly separate
configuration from user code by putting everything in flink-conf.yaml. We
should *also* make it possible to override any of those values on the command
line when submitting a job.
> Make all configuration possible via flink-conf.yaml and CLI.
> ------------------------------------------------------------
>
> Key: FLINK-4947
> URL: https://issues.apache.org/jira/browse/FLINK-4947
> Project: Flink
> Issue Type: Improvement
> Components: DataStream API
> Reporter: Jamie Grier
>
> I think it's important to make all configuration possible via the
> flink-conf.yaml and the command line.
> As an example: To enable "externalizedCheckpoints" you must actually call
> the StreamExecutionEnvironment#enableExternalizedCheckpoints() method from
> your Flink program.
> Another example of this would be configuring the RocksDB state backend.
> I think it important to make deployment flexible and easy to build tools
> around. For example, the infrastructure teams that make these configuration
> decisions and provide tools for deploying Flink apps, will be different from
> the teams deploying apps. The team writing apps should not have to set all
> of this lower level configuration up in their programs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
