[
https://issues.apache.org/jira/browse/FLINK-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783962#comment-16783962
]
vinoyang commented on FLINK-10506:
----------------------------------
[~till.rohrmann] I agree with you. As we have communicated before, some of the
bigger changes I won't start before I get your idea. In fact, we are very
concerned about this feature, I am currently reading the design documentation
and thinking about it. I know that the community is busy publishing Flink 1.8
recently, and I hope that this feature will be launched after the 1.8 release.
> Introduce minimum, target and maximum parallelism to JobGraph
> -------------------------------------------------------------
>
> Key: FLINK-10506
> URL: https://issues.apache.org/jira/browse/FLINK-10506
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.7.0
> Reporter: Till Rohrmann
> Assignee: vinoyang
> Priority: Major
> Fix For: 1.8.0
>
>
> In order to run a job with a variable parallelism, one needs to be able to
> define the minimum and maximum parallelism for an operator as well as the
> current target value. In the first implementation, minimum could be 1 and
> maximum the max parallelism of the operator if no explicit parallelism has
> been specified for an operator. If a parallelism p has been specified (via
> setParallelism(p)), then minimum = maximum = p. The target value could be the
> command line parameter -p or the default parallelism.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
