>>>
>>>
>>> Thias
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> [1]
>>> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/serialization/schema_evolution/#kryo-cannot-b
ps://nightlies.apache.org/flink/flink-docs-master/docs/libs/state_processor_api/
>>
>> [3]
>> https://flink.apache.org/news/2020/04/15/flink-serialization-tuning-vol-1.html
>>
>>
>>
>>
>>
>>
>>
>> *From:* Vishal Santoshi
>> *Sent
e-used-for-schema-evolution
>
> [2]
> https://nightlies.apache.org/flink/flink-docs-master/docs/libs/state_processor_api/
>
> [3]
> https://flink.apache.org/news/2020/04/15/flink-serialization-tuning-vol-1.html
>
>
>
>
>
>
>
> *From:* Vishal Santoshi
>
, September 16, 2022 1:17 AM
To: user
Subject: Re: A question about restoring state with an additional variable with
kryo
⚠EXTERNAL MESSAGE – CAUTION: Think Before You Click ⚠
The exception thrown is as follows. I realize that it is trying to read the
long value. How do I signal to kryo that it is OK
The exception thrown is as follows. I realize that it is trying to read the
long value. How do I signal to kryo that it is OK and that he object can
have a default value
Caused by: java.io.EOFException: No more bytes left.
at org.apache.flink.api.java.typeutils.runtime.NoFetchingInput.require(
<< 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 tri
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 Cla
