Scala case class state evolution

[Elias Levy]

Currently it is impossible to evolve a Scala case class by adding a new field to it that is stored as managed state using the default Flink serializer and restore a the job from a savepoint created using the previous version of the class, correct?

[Hequn Cheng]

Hi Elias,

From my understanding, you can't do this since the state will no longer be compatible.

Best, Hequn

On Wed, Oct 3, 2018 at 6:32 AM Elias Levy <[hidden email]> wrote:

Currently it is impossible to evolve a Scala case class by adding a new field to it that is stored as managed state using the default Flink serializer and restore a the job from a savepoint created using the previous version of the class, correct?

[Fabian Hueske-2]

I know that Gordon (in CC) has looked closer into this problem. 

He should be able to share restrictions and maybe even workarounds.

Best, Fabian 

Hequn Cheng <[hidden email]> schrieb am Mi., 3. Okt. 2018, 05:09:

Hi Elias,

From my understanding, you can't do this since the state will no longer be compatible.

Best, Hequn

On Wed, Oct 3, 2018 at 6:32 AM Elias Levy <[hidden email]> wrote:

Currently it is impossible to evolve a Scala case class by adding a new field to it that is stored as managed state using the default Flink serializer and restore a the job from a savepoint created using the previous version of the class, correct?