You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tao Meng (JIRA)" <ji...@apache.org> on 2017/02/21 10:22:44 UTC

[jira] [Commented] (FLINK-5808) Missing verification for setParallelism and setMaxParallelism

    [ https://issues.apache.org/jira/browse/FLINK-5808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875748#comment-15875748 ] 

Tao Meng commented on FLINK-5808:
---------------------------------

Maybe it depends on which is the first value to be set that one value clashes with the other one.
For example: When we called {{setMaxParallelism}} before {{setParallelism}}, the {{parallelism}} is the global default value. So if global default {{parallelism}} is bigger than {{maxParallelism}} which we want to set, should we verification it.

> Missing verification for setParallelism and setMaxParallelism
> -------------------------------------------------------------
>
>                 Key: FLINK-5808
>                 URL: https://issues.apache.org/jira/browse/FLINK-5808
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API
>            Reporter: Aljoscha Krettek
>
> When {{setParallelism()}} is called we don't verify that it is <= than max parallelism. Likewise, when {{setMaxParallelism()}} is called we don't check that the new value doesn't clash with a previously set parallelism.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)