But it will be two TypeSerializerConfigSnapshots, otherwise unclear how
TypeSerializer2 will able to check compatibility?
Thanks,
Alexey
________________________________
From: Congxian Qiu <qcx978132...@gmail.com>
Sent: Thursday, February 7, 2019 8:14 PM
To: Alexey Trenikhun
Cc: user@flink.apache.org
Subject: Re: MapState - TypeSerializer
Hi, Alexey
In your case, only TypeSerializer2 will be stored in meta information. and
TypeSerializer2 and TypeSeriaizer1 have to be compatible.
Best,
Congxian
Alexey Trenikhun <yen...@msn.com<mailto:yen...@msn.com>> 于2019年2月8日周五 上午10:39写道：
What if I’m using RocksDB, and MapState had single entry and TypeSerializer1,
then we take save point upgrade job (TypeSerializer2), put new entry, at that
point we have two entries written by different serializers, so both
TypeSerializers should be stored in meta information?
Thanks,
Alexey
________________________________
From: Andrey Zagrebin
<and...@data-artisans.com<mailto:and...@data-artisans.com>>
Sent: Wednesday, November 28, 2018 2:23 AM
To: Alexey Trenikhun
Cc: user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: MapState - TypeSerializer
Hi Alexey,
it is written once per state name in its meta information, apart from user data
entries.
Best,
Andrey
On 28 Nov 2018, at 04:56, Alexey Trenikhun
<yen...@msn.com<mailto:yen...@msn.com>> wrote:
Hello,
Flink documentation states that “TypeSerializers and
TypeSerializerConfigSnapshots are written as part of checkpoints along with the
state values”, in context of MapState, does it mean TypeSerializer per each
MapState entry or only once per state?
Alexey
