[
https://issues.apache.org/jira/browse/FLINK-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289451#comment-16289451
]
Xingcan Cui commented on FLINK-8236:
------------------------------------
Yes, maybe we should consider unifying them since in some classes (e.g.,
{{DataSink.java}}) the logic is like that
{code:java}
public DataSink<T> setParallelism(int parallelism) {
Preconditions.checkArgument(parallelism > 0 || parallelism ==
ExecutionConfig.PARALLELISM_DEFAULT, "The parallelism of an operator must be at
least 1.");
this.parallelism = parallelism;
return this;
}
{code}
> Allow to set the parallelism of table queries
> ---------------------------------------------
>
> Key: FLINK-8236
> URL: https://issues.apache.org/jira/browse/FLINK-8236
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.4.0
> Reporter: Timo Walther
> Assignee: Xingcan Cui
>
> Right now the parallelism of a table program is determined by the parallelism
> of the stream/batch environment. E.g., by default, tumbling window operators
> use the default parallelism of the environment. Simple project and select
> operations have the same parallelism as the inputs they are applied on.
> While we cannot change forwarding operations because this would change the
> results when using retractions, it should be possible to change the
> parallelism for operators after shuffling operations.
> It should be possible to specify the default parallelism of a table program
> in the {{TableConfig}} and/or {{QueryConfig}}. The configuration per query
> has higher precedence that the configuration per table environment.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
