flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aljoscha Krettek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-6188) Some setParallelism() methods can't cope with default parallelism
Date Wed, 03 May 2017 09:35:04 GMT

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

Aljoscha Krettek commented on FLINK-6188:

Removing blocker status since FLINK-5808 was reverted.

> 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.3.0, 1.2.1
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
> 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

View raw message