[jira] [Updated] (FLINK-26358) Operator maxParallelism is lost during chaining

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ 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 pull-request-available stale-major  (was: auto-deprioritized-critical pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 60 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Major
>              Labels: auto-deprioritized-critical, pull-request-available, stale-major
>
> 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)