[
https://issues.apache.org/jira/browse/FLINK-4947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-4947:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: API / DataStream
> Reporter: Jamie Grier
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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
(v8.20.1#820001)
