Re: Job downgrade

t; Alexey > > -- > *From:* Tzu-Li (Gordon) Tai > *Sent:* Thursday, March 4, 2021 12:58:01 AM > *To:* Alexey Trenikhun > *Cc:* Piotr Nowojski ; Flink User Mail List < > user@flink.apache.org> > *Subject:* Re: Job downgrade > > Hi Alexey, > > Are you using the heap bac

Re: Job downgrade

Hi Gordon, I was using RocksDB backend Alexey From: Tzu-Li (Gordon) Tai Sent: Thursday, March 4, 2021 12:58:01 AM To: Alexey Trenikhun Cc: Piotr Nowojski ; Flink User Mail List Subject: Re: Job downgrade Hi Alexey, Are you using the heap backend? If that's

Re: Job downgrade

; “rollback” to version 1+. > > -- > *From:* Piotr Nowojski > *Sent:* Wednesday, March 3, 2021 11:47:45 AM > *To:* Alexey Trenikhun > *Cc:* Flink User Mail List > *Subject:* Re: Job downgrade > > Hi, > > I'm not sure what's the reason behind this. Probably classes are

Re: Job downgrade

expected “rollback” to version 1+. From: Piotr Nowojski Sent: Wednesday, March 3, 2021 11:47:45 AM To: Alexey Trenikhun Cc: Flink User Mail List Subject: Re: Job downgrade Hi, I'm not sure what's the reason behind this. Probably classes are somehow attached

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

Job downgrade

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