You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fabian Paul (Jira)" <ji...@apache.org> on 2022/03/07 07:50:00 UTC

[jira] [Closed] (FLINK-26453) execution.allow-client-job-configurations not checked for executeAsync

     [ https://issues.apache.org/jira/browse/FLINK-26453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fabian Paul closed FLINK-26453.
-------------------------------

> execution.allow-client-job-configurations not checked for executeAsync
> ----------------------------------------------------------------------
>
>                 Key: FLINK-26453
>                 URL: https://issues.apache.org/jira/browse/FLINK-26453
>             Project: Flink
>          Issue Type: Bug
>          Components: API / DataStream
>    Affects Versions: 1.15.0
>            Reporter: Marios Trivyzas
>            Assignee: Fabian Paul
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> * *checkNotAllowedConfigurations()* should be called by  *StreamContextEnvironment#executeAsync()*
>  * Description of the *DeploymentOption* should be more clear, and it's not only checked by application mode.
>  * When using a config option which is the same as the one in the environment *(flink-conf.yaml + CLI options)*  we still throw an exception, and we also throwing the exception even if the option is not in the environment, but it's the default value of the option anyway. Should we check for those cases, or should we at least document them and say explicitly that no config option is allowed to be set, if the *execution.allow-client-job-configurations* is set to {*}false{*}?
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)