[
https://issues.apache.org/jira/browse/FLINK-25206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17498969#comment-17498969
]
Robert Metzger commented on FLINK-25206:
----------------------------------------
Using
{code}
env.getConfig().setGlobalJobParameters(parameters);
{code}
doesn't work after this change:
{code}
Caused by: org.apache.flink.client.program.MutatedConfigurationException:
Configuration object ExecutionConfig changed.
at
org.apache.flink.client.program.StreamContextEnvironment.checkNotAllowedConfigurations(StreamContextEnvironment.java:143)
~[flink-dist-flink-nightly.jar:flink-nightly]
at
org.apache.flink.client.program.StreamContextEnvironment.execute(StreamContextEnvironment.java:119)
~[flink-dist-flink-nightly.jar:flink-nightly]
{code}
I see the following options to move forward:
- deprecate the "setGlobalJobParameters()"
- add an exception to the configuration check and allow these changes
WDYT?
> 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)
