[
https://issues.apache.org/jira/browse/FLINK-22257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364745#comment-17364745
]
Timo Walther commented on FLINK-22257:
--------------------------------------
We should include [~AHeise] here as well. This is clearly also an SDK topic
that we've started in 2019 but never completed. The prefixes of option names
(e.g. `pipeline.`) mostly represent the proposed design but allowing to define
additional areas where options apply programmatically is a good idea.
> Clarify Flink ConfigOptions Usage
> ---------------------------------
>
> Key: FLINK-22257
> URL: https://issues.apache.org/jira/browse/FLINK-22257
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Reporter: Fabian Paul
> Priority: Minor
>
> For users, it is hard to determine which ConfigOptions are relevant for the
> different stages of a Flink application.
> Beginning from the translation of the user program to the execution on the
> cluster. In particular which options can be configured through the different
> channels.
> * Cluster configuration (i.e. flink-conf.yaml)
> * Application configuration, code-based
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
