[
https://issues.apache.org/jira/browse/FLINK-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498978#comment-17498978
]
Fabian Paul commented on FLINK-25206:
-------------------------------------
Maybe I am not fully understanding the problem because it sounds to me like the
user program's main method did the call and that is not allowed. In this case
all `env.getConfig().setXXXX` because they may overwrite cluster
configurations.
In the long run we definitely have to rework how the configurations are
currently handled but we agreed that it is out of the scope of this ticket and
might be also a Flink 2.0 to allow breaking changes.
> Add config option to disable configurations in the user program
> ---------------------------------------------------------------
>
> Key: FLINK-25206
> URL: https://issues.apache.org/jira/browse/FLINK-25206
> Project: Flink
> Issue Type: New Feature
> Components: Client / Job Submission, Runtime / Coordination
> Affects Versions: 1.15.0
> Reporter: Fabian Paul
> Assignee: Fabian Paul
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.15.0
>
>
> If you run a large number of Flink jobs usually there is a governing entity
> controlling and ensuring the execution of all clusters.
> To ease the control over configurations we want to enable setting a
> configuration that disallows configurations in the user program.
> By default, this is turned off so the normal execution will not be affected.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
