You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2020/09/03 05:05:00 UTC
[jira] [Comment Edited] (FLINK-19128) Remove the runtime execution
configuration in sql-client-defaults.yaml
[ https://issues.apache.org/jira/browse/FLINK-19128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189839#comment-17189839 ]
Nicholas Jiang edited comment on FLINK-19128 at 9/3/20, 5:04 AM:
-----------------------------------------------------------------
Hi, [~jark], do you mean that the first step you mentioned should remove this sql-client-defaults.yaml configuration file, and use flink-conf.yaml as the default configuration file (DEFAULT_ENV_FILE) for LocalExecutor?
was (Author: nicholasjiang):
Hi, [~jark], do you mean that the first step you mentioned should remove this sql-client-defaults.yaml configuration file, and use flink-conf.yaml as the default configuration file?
And the DEFAULT_ENV_FILE of LocalExecutor could be flink-conf.yaml.
> Remove the runtime execution configuration in sql-client-defaults.yaml
> ----------------------------------------------------------------------
>
> Key: FLINK-19128
> URL: https://issues.apache.org/jira/browse/FLINK-19128
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / Client
> Reporter: Jark Wu
> Priority: Major
>
> Currently, {{sql-client-defaults.yaml}} sets some runtime execution configuration by defualt, e.g. parallelism, restart strategy. This is very confusing. Because users are confused why paralleslim is changed in {{flink-conf.yaml}} but it doesn't work.
> I think the community had an agreement that SQL CLI shouldn't provide a new set of runtime configuration. As a first step, I suggest to remove these configurations defined in {{sql-client-defaults.yaml}}, to make the configurations in {{flink-conf.yaml}} work by default.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)