[
https://issues.apache.org/jira/browse/FLINK-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135421#comment-17135421
]
Dawid Wysakowicz commented on FLINK-18161:
------------------------------------------
Thanks for the discussion. I don't know if it is the right solution, but I'd go
with:
For 1.11 I'd keep the old behaviour and make the {{execution.parallelism}}
work. I'd not care too much to make the {{parallelism.default}} work well in
that version, as it was not supported, it is not documented and it's more of a
coincidence it works. To achieve that I'd do what [~jark] is suggesting,
meaning instead of using {{env.setParallelism()}} I'd use
{{set("parallelism.default", ...)}} for the {{execution.parallelism}}.
For 1.12 I'd be ok with removing the sql-cli specific parameters and supporting
the common parameters. Probably though I'd still support the old parameters for
one more version and thrown either an exception or very prominent warning that
this setting will be removed in the next version.
> 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)
