[
https://issues.apache.org/jira/browse/FLINK-26358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-26358:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
pull-request-available (was: auto-deprioritized-critical
pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days 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.
> Operator maxParallelism is lost during chaining
> -----------------------------------------------
>
> Key: FLINK-26358
> URL: https://issues.apache.org/jira/browse/FLINK-26358
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.14.3, 1.15.0
> Reporter: Fabian Paul
> Priority: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> pull-request-available
>
> During the generation of the JobGraph from the StreamGraph the maxParallelism
> of the chained operators is lost so the maxParallelism written to a snapshot
> might not reflect the real maxParallelism of the operator.
> If a user now unchains the operator it is not possible to restore a snapshot
> anymore because the maxParallelism of the operator and the snapshot do not
> match anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
