[
https://issues.apache.org/jira/browse/FLINK-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16346348#comment-16346348
]
ASF GitHub Bot commented on FLINK-8407:
---------------------------------------
Github user xccui commented on the issue:
https://github.com/apache/flink/pull/5369
Ah ha, it doesn't matter. 😄 The test has been updated. Actually, I wanted
to ensure that all the partitioning methods should cause the exception.
However, that would be fussy and thus I only kept the broadcasted one.
> Setting the parallelism after a partitioning operation should be forbidden
> --------------------------------------------------------------------------
>
> Key: FLINK-8407
> URL: https://issues.apache.org/jira/browse/FLINK-8407
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
> Reporter: Xingcan Cui
> Assignee: Xingcan Cui
> Priority: Major
>
> Partitioning operations ({{shuffle}}, {{rescale}}, etc.) for a {{DataStream}}
> create new {{DataStreams}}, which allow the users to set parallelisms for
> them. However, the {{PartitionTransformations}} in these returned
> {{DataStreams}} will only add virtual nodes, whose parallelisms could not be
> specified, in the execution graph. We should forbid users to set the
> parallelism after a partitioning operation since they won't actually work.
> Also the corresponding documents should be updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
