[
https://issues.apache.org/jira/browse/FLINK-26916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514592#comment-17514592
]
Gyula Fora commented on FLINK-26916:
------------------------------------
I think as soon as there is a straightforward way of accessing the last
checkpoint, we can easily modify the last-state upgrade implementation and make
it nicer by properly shutting down clusters.
Unfortunately this is not possible at the moment hence the current mechanism.
We also need to consider supporting older flink versions (1.14 and up) so the
current mechanism might need to stick around for some time
> The Operator ignores job related changes (jar, parallelism) during last-state
> upgrades
> --------------------------------------------------------------------------------------
>
> Key: FLINK-26916
> URL: https://issues.apache.org/jira/browse/FLINK-26916
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-0.1.0, kubernetes-operator-1.0.0
> Reporter: Matyas Orhidi
> Assignee: Yang Wang
> Priority: Blocker
> Labels: pull-request-available
> Fix For: kubernetes-operator-0.1.0
>
>
> RC: The old jobgraph is being reused when resuming
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
