[
https://issues.apache.org/jira/browse/FLINK-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135384#comment-17135384
]
godfrey he commented on FLINK-18161:
------------------------------------
[~jark], thanks for the suggestion, but I don't think that could simplify
design. First, If sql-client's configuration accept {{parallelism.default}}, we
also should handle the conflict. Second, when users execute
{{execution.parallelism=12}} and then execute {{set}} command to list all
properties, they find {{execution.parallelism}} does not exist . Last, we must
handle this special case in {{ConfigurationEntry}}.
> 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
> Assignee: godfrey he
> Priority: Critical
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> 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)
