[
https://issues.apache.org/jira/browse/FLINK-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135028#comment-17135028
]
Jark Wu commented on FLINK-18161:
---------------------------------
+1 to remove the duplicate congiuratiion in SQL CLI in the future.
For now, I would suggest to make {{execution.parallelism}} as a synonym for
{{parallelism.default}}. The set of {{execution.parallelism}} will be
translated to {{parallelism.default}}. So there is no priority problem, it's
just depends on the set order. And I guess this will simplify much things?
> 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)
