for a good solution.
From: Robert Metzger
Date: Wednesday, August 4, 2021 at 10:21 AM
To: Weston Woods
Cc: "user@flink.apache.org" , Timo Walther
Subject: Re: Savepoint class refactor in 1.11 causing restore from 1.9
savepoint to fail
Hi Weston,
Oh indeed, you are right! I qui
untime?
>
>
>
>
>
>
>
> *From: *Robert Metzger
> *Date: *Tuesday, August 3, 2021 at 11:52 AM
> *To: *Weston Woods
> *Cc: *"user@flink.apache.org"
> *Subject: *Re: Savepoint class refactor in 1.11 causing restore from 1.9
> savepoint to fail
>
>
&g
, August 3, 2021 at 11:52 AM
To: Weston Woods
Cc: "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 acros
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 migr
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 clas
