[
https://issues.apache.org/jira/browse/FLINK-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059493#comment-16059493
]
sunjincheng commented on FLINK-6966:
------------------------------------
Hi [~fhueske] That's true. I got it. In our side we already meet that problem.
we can not increase the parallelism of an operator if we do not set
{{maxParallelism}}.
* About {{maxParallelism}}, it is not easy to set every operator's
{{maxParallelism}} by SQL/TableAPI. I think we can set global
{{maxParallelism}} by {{StreamExecutionEnvironment}}. Of course we can define a
default value for user or give a hint message if the user is not set.
* About UID, for the first version I think we can just deal with the operators
which are generated by {{DataStreamRel#translateToPlan}}.
Please let me know what you think?
Hi [~jark] I think {{QueryConfig }} is difficult to set set every operator's
{{maxParallelism}}, If we want a global value, the
{{StreamExecutionEnvironment}} is enough. What do you think?
Feel free to correct me If there are any incorrect describe. [~fhueske] [~jark]
> Add maxParallelism and UIDs to all operators generated by the Table API / SQL
> -----------------------------------------------------------------------------
>
> Key: FLINK-6966
> URL: https://issues.apache.org/jira/browse/FLINK-6966
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.4.0
> Reporter: Fabian Hueske
>
> At the moment, the Table API does not assign UIDs and the max parallelism to
> operators (except for operators with parallelism 1).
> We should do that to avoid problems when rescaling or restarting jobs from
> savepoints.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
