Robert, Thanks for your reply. How should I interpret the savepoint compatibility table here https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/ops/upgrading/#compatibility-table if a 1.9 savepoint cannot be restored into a 1.11 runtime?
From: Robert Metzger <rmetz...@apache.org> Date: Tuesday, August 3, 2021 at 11:52 AM To: Weston Woods <wwo...@spireon.com> Cc: "user@flink.apache.org" <user@flink.apache.org> Subject: Re: Savepoint class refactor in 1.11 causing restore from 1.9 savepoint to fail Hi Weston, I haven never looked into the savepoint migration code paths myself, but I know that savepoint migration across multiple versions is not supported (1.9 can only migrate to 1.10, not 1.11). We have test coverage for these migrations, and I would be surprised if this "Savepoint" class migration is not covered in these tests. Have you tried upgrading from 1.9 to 1.10, and then from 1.10 to 1.11? On Fri, Jul 30, 2021 at 11:53 PM Weston Woods <wwo...@spireon.com<mailto:wwo...@spireon.com>> wrote: I am unable to restore a 1.9 savepoint into a 1.11 runtime for the very interesting reason that the Savepoint class was renamed and repackaged between those two releases. Apparently a Kryo serializer has that class registered in the 1.9 runtime. I can’t think of a good reason for that class to be registered with Kryo; none of the job operators reference any such thing. Yet there it is causing the following exception and preventing upgrade to a new runtime.
