What you want is a Flink 1.x to Flink 2.x migration tool; that's much more
complicated than simply migrating Kryo because there were lots of compatibility
breaking changes beyond the Kryo upgrade.
Flink 1.x used Kryo by default everywhere. Flink 2.0 does not. That's a
compatibility breaking cha
16:44
To: dev@flink.apache.org
Cc: ches...@apache.org , guowei...@apache.org
, Xintong Song ,
zake...@apache.org , Chen Zhanghao
, Martijn Visser
Subject: [EXTERNAL] FW: Kryo v2 to v5 migration tool
Hi all,
I was reviewing and realised from pull request 26444 [1] which is to do with
removing
Hi all,
I was reviewing and realised from pull request 26444 [1] which is to do with
removing data associated with eversion state for unit tests. I can look into
creating a migration tool and have copied in some of the people who have been
involved with this for feedback / thoughts on the appro
