You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/03 10:14:41 UTC
[jira] [Commented] (FLINK-6188) Some setParallelism() methods can't
cope with default parallelism
[ https://issues.apache.org/jira/browse/FLINK-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953223#comment-15953223 ]
ASF GitHub Bot commented on FLINK-6188:
---------------------------------------
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3616
@greghogan @kl0u I addressed your comments.
> Some setParallelism() methods can't cope with default parallelism
> -----------------------------------------------------------------
>
> Key: FLINK-6188
> URL: https://issues.apache.org/jira/browse/FLINK-6188
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
> Affects Versions: 1.2.1
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Blocker
> Fix For: 1.2.1
>
>
> Recent changes done for FLINK-5808 move default parallelism manifestation from eager to lazy, that is, the parallelism of operations that don't have an explicit parallelism is only set when generating the JobGraph. Some {{setParallelism()}} calls, such as {{SingleOutputStreamOperator.setParallelism()}} cannot deal with the fact that the parallelism of an operation might be {{-1}} (which indicates that it should take the default parallelism when generating the JobGraph).
> We should either revert the changes that fixed another user-facing bug for version 1.2.1 or fix the methods.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)