[
https://issues.apache.org/jira/browse/FLINK-32983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruan Hang updated FLINK-32983:
------------------------------
Fix Version/s: 2.3.0
(was: 2.2.0)
> Support setting env.java.opts.all & env.java.opts.cli configs via dynamic
> properties on the CLI side
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-32983
> URL: https://issues.apache.org/jira/browse/FLINK-32983
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client, Deployment / Scripts
> Affects Versions: 2.1.0
> Reporter: Zhanghao Chen
> Priority: Minor
> Fix For: 2.3.0
>
>
> *Problem*
> The following configs are supposed to be supported:
> |h5. env.java.opts.all|(none)|String|Java options to start the JVM of all
> Flink processes with.|
> |h5. env.java.opts.client|(none)|String|Java options to start the JVM of the
> Flink Client with.|
> However, the two configs only takes effect on the Client side when they are
> set in the flink-conf files. In other words, configs set via -D or-yD on the
> CLI will not take effect, which is counter-intuitive and makes configuration
> less flexible.
>
> *Proposal*
> Add logic to parse configs set via -D or-yD in config.sh and make them has a
> higher precedence over configs set in flink-conf.yaml for env.java.opts.all &
> env.java.opts.client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
