Hi, I was looking at the docs [<https://nightlies.apache.org/flink/flink-docs-release-2.0/docs/dev/table/concepts/overview/#stateful-upgrades-and-evolution>1] where it says : Currently, the framework cannot guarantee that state can be mapped from a savepoint to a new table operator topology. In other words: Savepoints are only supported if both the query and the Flink version remain constant.
When we say table operator topology - does this mean: * The Calcite relational algebra prior to planning and optimisation 1. or * After the planning and optimisation I wanted to confirm that the Calcite planning and optimisation does not effect savepoint migration between releases. The main migration consideration would be around saving state associated with a type that has a non standard serialiser (like Kryo) or a custom serialiser. Kind regards, David. [1] https://nightlies.apache.org/flink/flink-docs-release-2.0/docs/dev/table/concepts/overview/#stateful-upgrades-and-evolution Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: Building C, IBM Hursley Office, Hursley Park Road, Winchester, Hampshire SO21 2JN
