flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-4947) Make all configuration possible via flink-conf.yaml and CLI.
Date Mon, 23 Jan 2017 12:25:27 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Robert Metzger updated FLINK-4947:
    Fix Version/s:     (was: 1.2.0)

> 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

View raw message