[jira] [Updated] (FLINK-27516) The config execution.attached doesn't take effect when not set by Cli param

["Liu (Jira)" <ji...@apache.org>]

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

Liu updated FLINK-27516:
------------------------
    Summary: The config execution.attached doesn't take effect when not set by Cli param  (was: The config execution.attached doesn't take effect wen not set by Cli param)

> The config execution.attached doesn't take effect when not set by Cli param
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-27516
>                 URL: https://issues.apache.org/jira/browse/FLINK-27516
>             Project: Flink
>          Issue Type: Improvement
>          Components: Client / Job Submission
>    Affects Versions: 1.16.0
>            Reporter: Liu
>            Priority: Minor
>
> The config execution.attached's default value is false. But no matter what value we set, it takes no effect. After digging in, we find that it is only affected by Cli param as following:
>  # If we don't specify -d or -yd, the member detachedMode in ProgramOptions is set to false.
>  # In method applyToConfiguration, the execution.attached is set true.
>  # No matter what value is set to execution.attached, it take no effect.
> If -d or -yd is not set, we should use the config execution.attached. Since the actual attach mode is using for a long time, we may need to change execution.attached's default value to true after the modification.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)