<< How do I make sure that when reconstituting the state, kryo does not
complain? It tries to map the previous state to the new definition of Class
A and complains that it cannot read the value for `String b`.

>> How do I make sure that when reconstituting the state, kryo does not
complain? It tries to map the previous state to the new definition of Class
A and complains that it cannot read the value for `long b`.

Sorry a typo


On Thu, Sep 15, 2022 at 7:04 PM Vishal Santoshi <vishal.santo...@gmail.com>
wrote:

> I have state in rocksDB that represents say
>
> class A {
>   String a
> }
>
> I now change my class and add another variable
>
>
> Class A {
>   String a;
>   long b = 0;
> }
>
> How do I make sure that when reconstituting the state, kryo does not
> complain? It tries to map the previous state to the new definition of Class
> A and complains that it cannot read the value for `String b`.
>
> Unfortunately the state is not using POJO serializer.
>
> Thanks and Regards.
>
> Vishal
>
>
>
>
>

Reply via email to