If I copy class A into version 1+ it works. But it is the problem from CD perspective - I want to introduce feature which required new state: 1st I need make version 1+ with class B, but no other changes, then version 2 with class B and logic changes, upgrade job and if job doesn’t do what expected “rollback” to version 1+.
________________________________ From: Piotr Nowojski <pnowoj...@apache.org> Sent: Wednesday, March 3, 2021 11:47:45 AM To: Alexey Trenikhun <yen...@msn.com> Cc: Flink User Mail List <user@flink.apache.org> Subject: Re: Job downgrade Hi, I'm not sure what's the reason behind this. Probably classes are somehow attached to the state and this would explain why you are experiencing this issue. I've asked someone else from the community to chip in, but in the meantime, can not you just prepare a new "version 1" of the job, with just some empty `class B` on the class path? Or if this doesn't work, just copy the whole `class B` from version 2? Best, Piotrek sob., 27 lut 2021 o 19:10 Alexey Trenikhun <yen...@msn.com<mailto:yen...@msn.com>> napisał(a): Hello, Let's have version 1 of my job uses keyed state with name "a" and type A, which some Avro generated class. Then I upgrade to version 2, which in addition uses keyed state "b" and type B (another concrete Avro generated class), I take savepoint with version 2 and decided to downgrade to version 1 and start with taken savepoint, can I do it? On one hand, version 1 doesn't have state "b", but seems Flink still tries to create call restoreSerializer and it tries to read runtimeType (`class B`) which is not available in version 1 Thanks, Alexey
