[FLINK-5473] setMaxParallelism() higher than 1 is possible on non-parallel operators

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.0
• Fix Version/s: 1.2.0, 1.3.0
• Component/s: API / DataStream
• Assignee: Stefan Richter
• Reporter: Robert Metzger
• Created: 12/Jan/17 15:22
• Updated: 23/Mar/23 09:21
• Resolved: 24/Jan/17 14:54

Description

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.

Issue Links

• causes: FLINK-29822 Fix wrong description in comments of StreamExecutionEnvironment#setMaxParallelism()
• links to: GitHub Pull Request #3182