You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/10/11 18:17:00 UTC
[jira] [Commented] (FLINK-29588) Add Flink Version and Application Version to Savepoint properties
[ https://issues.apache.org/jira/browse/FLINK-29588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616018#comment-17616018 ]
Gyula Fora commented on FLINK-29588:
------------------------------------
What do you mean by appVersion here?
> Add Flink Version and Application Version to Savepoint properties
> -----------------------------------------------------------------
>
> Key: FLINK-29588
> URL: https://issues.apache.org/jira/browse/FLINK-29588
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0
> Reporter: Clara Xiong
> Priority: Major
>
> It is common that users need to upgrade long running FlinkDeployment's. An application upgrade or a major Flink upgrade might break the applications due to schema incompatibilities, especially the latter([Link)|https://nightlies.apache.org/flink/flink-docs-master/docs/ops/upgrading/#compatibility-table]. In this case, the users need to manually restore to a savepoint that is compatible with the version the user wants to try or re-process. Currently Flink Operator returns a list of completed Savepoint's for a FlinkDeployment. It will be helpful that the Savepoint's in SavepointHistory have the properties for Flink Version and application version so users can easily determine which savepoint to use.
>
> * {{String flinkVersion}}
> * {{String appVersion}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)