[FLINK-6188] Some setParallelism() methods can't cope with default parallelism

• Type: Bug
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.2.1, 1.3.0
• Component/s: API / DataStream
• Labels: auto-deprioritized-major auto-deprioritized-minor pull-request-available
• Assignee: Unassigned
• Reporter: Aljoscha Krettek
• Created: 25/Mar/17 08:28
• Updated: 04/Jan/22 10:39

Description

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.

Issue Links

• is broken by: FLINK-5808 Missing verification for setParallelism and setMaxParallelism
• links to: GitHub Pull Request #3616
• links to: GitHub Pull Request #3616