[
https://issues.apache.org/jira/browse/FLINK-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126788#comment-17126788
]
Dawid Wysakowicz commented on FLINK-18161:
------------------------------------------
The problem is that the command will result in setting the parallelism directly
on the underlying StreamExecutionEnvironment/BatchExecutionEnvironment.
At the same time the {{TableConfig}} is populated with a {{Configuration}}
({{LocalExecutor#flinkConfig}}) populated from the {{GlobalConfiguration}}
which sets the {{parallelism.default}}.
This setting always overwrites the parallelism of the
{{StreamExecutionEnvironment}}
The flow is as follows:
1. We set value of {{execution.parallelism}} through
{{StreamExecutionEnvironment#setParallelism}}
2. We set value of {{parallelism.default}} from TableConfig#configuration on
{{StreamExecutionEnvironment}} effectively overwriting the previous setting.
> Changing parallelism is not possible in sql-client.sh
> -----------------------------------------------------
>
> Key: FLINK-18161
> URL: https://issues.apache.org/jira/browse/FLINK-18161
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.11.0
> Reporter: Robert Metzger
> Priority: Critical
>
> I tried using
> {code}
> SET execution.parallelism=12
> {code}
> and changing the parallelism in the configuration file.
> My SQL queries were always running with p=1 for all operators.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
