[
https://issues.apache.org/jira/browse/FLINK-25217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695881#comment-17695881
]
Jing Ge commented on FLINK-25217:
---------------------------------
Hi [~twalthr] , I'd like to (slowly) start working on this topic. Afaik, there
is one more important and hard task to do - make the upgrade still work if the
internal implementation of operator/execNode has been changed among Flink minor
releases. Since I just started understanding the design and what happened in
the past, I might not describe it precisely. Please correct me if I am wrong.
Thanks!
> FLIP-190: Support Version Upgrades for Table API & SQL Programs
> ---------------------------------------------------------------
>
> Key: FLINK-25217
> URL: https://issues.apache.org/jira/browse/FLINK-25217
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API, Table SQL / Planner
> Reporter: Timo Walther
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
>
> Nowadays, the Table & SQL API is as important to Flink as the DataStream API.
> It is one of the main abstractions for expressing pipelines that perform
> stateful stream processing. Users expect the same backwards compatibility
> guarantees when upgrading to a newer Flink version as with the DataStream API.
> In particular, this means:
> * once the operator topology is defined, it remains static and does not
> change between Flink versions, unless resulting in better performance,
> * business logic (defined using expressions and functions in queries) behaves
> identical as before the version upgrade,
> * the state of a Table & SQL API program can be restored from a savepoint of
> a previous version,
> * adding or removing stateful operators should be made possible in the
> DataStream API.
> The same query can remain up and running after upgrades.
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191336489
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
