[
https://issues.apache.org/jira/browse/FLINK-5342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759971#comment-15759971
]
godfrey he edited comment on FLINK-5342 at 12/19/16 3:35 AM:
-------------------------------------------------------------
at present， we can use TableConfig to tune the parallelism of key operators
which include shuffle operator (aggregator, sort, join, union), source operator
and sink operator. And flink optimizer should ensure that other operators
should be chained to previous operator as possible.
was (Author: godfreyhe):
at present， we can use TableConfig to tune the parallelism of key operators
which include shuffle operator (aggregator, sort, join, union), source operator
and sink operator. And flink optimizer should ensure that other operators
should be chained as possible.
> Setting the parallelism automatically for operators base on cost model
> ----------------------------------------------------------------------
>
> Key: FLINK-5342
> URL: https://issues.apache.org/jira/browse/FLINK-5342
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: godfrey he
>
> On Flink table API, a query will be translated to operators without
> parallelism. And user do not know even do not care the target operators
> translated from query. So it's better to set the parallelism automatically
> for each operator base on cost model.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
