flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-5473) setMaxParallelism() higher than 1 is possible on non-parallel operators
Date Mon, 23 Jan 2017 15:41:26 GMT

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

ASF GitHub Bot commented on FLINK-5473:

Github user StefanRRichter commented on the issue:


> setMaxParallelism() higher than 1 is possible on non-parallel operators
> -----------------------------------------------------------------------
>                 Key: FLINK-5473
>                 URL: https://issues.apache.org/jira/browse/FLINK-5473
>             Project: Flink
>          Issue Type: Bug
>          Components: DataStream API
>    Affects Versions: 1.2.0
>            Reporter: Robert Metzger
>            Assignee: Stefan Richter
> While trying out Flink 1.2, I found out that you can set a maxParallelism higher than
1 on a non-parallel operator.
> I think we should have the same semantics as the setParallelism() method.
> Also, when setting a global maxParallelism in the execution environment, it will be set
as a default value for the non-parallel operator.
> When restoring a savepoint from 1.1, you have to set the maxParallelism to the parallelism
of the 1.1 job. Non-parallel operators will then also get the maxPar set to this value, leading
to an error on restore.
> So currently, users restoring from 1.1 to 1.2 have to manually set the maxParallelism
to 1 for all non-parallel operators.

This message was sent by Atlassian JIRA

View raw message