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

Flink Jira Bot commented on FLINK-6188:
---------------------------------------

This issue was labeled "stale-major" 7 ago and has not received any updates so 
it is being deprioritized. If this ticket is actually Major, please raise the 
priority and ask a committer to assign you the issue or revive the public 
discussion.


> 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: API / DataStream
>    Affects Versions: 1.2.1, 1.3.0
>            Reporter: Aljoscha Krettek
>            Priority: Major
>              Labels: pull-request-available, stale-major
>
> 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
(v8.3.4#803005)

Reply via email to