Ok, thanks.
From: Chesnay Schepler
Sent: Wednesday, January 13, 2021 11:46:15 AM
To: Alexey Trenikhun ; Flink User Mail List
Subject: Re: state reset(lost) on TM recovery
The FsStateBackend makes heavy use of hashcodes, so it must be stable.
On 1/13/2021 7:13
*From:* Chesnay Schepler
*Sent:* Tuesday, January 12, 2021 2:20 AM
*To:* Alexey Trenikhun ; Flink User Mail List
*Subject:* Re: state reset(lost) on TM recovery
Are the hashes of these object equal as well?
On 1/12/2021 3:59 AM
Mail List
Subject: Re: state reset(lost) on TM recovery
Are the hashes of these object equal as well?
On 1/12/2021 3:59 AM, Alexey Trenikhun wrote:
Hello,
Yes, I'm aware, and I used elements with same key, and logged getCurrentKey()
to ensure that key is same, but you are right in terms
t:* Monday, January 11, 2021 4:36 PM
*To:* Alexey Trenikhun ; Flink User Mail List
*Subject:* Re: state reset(lost) on TM recovery
Just do double-check, are you aware that ValueState within a
Keyed*Function is scoped to the key of the input element(s)? I.e., any
stored value is only accessible if
alizedSize];
dataInputView.read(data);
return parser.parseFrom(CodedInputStream.newInstance(data));
}
From: Chesnay Schepler
Sent: Monday, January 11, 2021 4:36 PM
To: Alexey Trenikhun ; Flink User Mail List
Subject: Re: state reset(lost) on TM recovery
Just do do
Just do double-check, are you aware that ValueState within a
Keyed*Function is scoped to the key of the input element(s)? I.e., any
stored value is only accessible if an element with the same key is
processed?
On 1/10/2021 7:18 PM, Alexey Trenikhun wrote:
Hello,
I'm using Flink 1.11.3, state
