Hi Tim, If I understand correctly, you need to deploy a new SQL statement in order to fix your issue? If so, the problem is that a new SQL statement might lead to a different execution plan which can't be restored. See https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/concepts/overview/#state-management for more details on this topic.
Best regards, Martijn On Fri, Dec 16, 2022 at 12:34 AM Timothy Bess <tdbga...@gmail.com> wrote: > Hi there, > > We have a pyflink/SQL job that has a bug that we fixed and are trying to > deploy. Here's the issue though. The job successfully restores from the > checkpoint, but has no recent savepoints. We can't seem to get it to accept > our new SQL unless we savepoint/restore, but we can't trigger a savepoint > since our bug is crashing the job. > > How do people generally get around issues like this without losing all > Flink state? It seems weird that I'd have to lose my Flink state > considering that I can successfully restore the checkpoint. I must be > missing something here. > > Thanks, > > Tim >
