[FLINK-4947] Make all configuration possible via flink-conf.yaml and CLI.

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Component/s: API / DataStream
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Jamie Grier
• Created: 27/Oct/16 19:14
• Updated: 05/Feb/22 22:55

Description

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.