[
https://issues.apache.org/jira/browse/FLINK-36577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004230#comment-18004230
]
Robert Metzger commented on FLINK-36577:
----------------------------------------
Thanks for clarifying the purpose of this PR. My imagination went wild on the
PR title and I thought you were thinking about implementing some kind of "Flink
state compatibility check" into the FlinkStateSnapshot source.
Imagine you have v1.1 of your Flink job, and a savepoint for it.
Now you've implemented v1.2, and you want to check if the savepoint cleanly
applies to the job.
I don't know who one would go about implementing it, and if the operator is the
right place .. but it's an interesting problem to think about.
We probably need to know the operator uuids from the JobGraph of v1.2 to see if
they match the uuids in the savepoint?
> Add compatibility check for FlinkStateSnapshot CRD
> --------------------------------------------------
>
> Key: FLINK-36577
> URL: https://issues.apache.org/jira/browse/FLINK-36577
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Mate Czagany
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.13.0
>
>
> There are already two CRD compatibility checks in the
> flink-kubernetes-operator-api POM (for FlinkDeployment and FlinkSessionJob),
> one should also be added for FlinkStateSnapshot.
>
> Requirement for this is to have the 1.10.0 version released.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
