Re: Details of the downsides of “falling back” to Kyro rather than using Flink’s built in serde

Hi Konstantin, Thank you! This is exactly what I was looking for. Thanks Kevin -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/

Re: Details of the downsides of “falling back” to Kyro rather than using Flink’s built in serde

Hi Kevin, there are no performance downsides to using Flink POJOs. You are just limited in the types you can use (e.g. you can not use Collections). In Flink 1.7 you might want to use Avro (SpecificRecord) for your state objects to benefit from Flink's built-in state schema evolution

Details of the downsides of “falling back” to Kyro rather than using Flink’s built in serde

Hi all, I was looking at https://ci.apache.org/projects/flink/flink-docs-stable/dev/types_serialization.html, and https://www.youtube.com/watch?v=euFMWFDThiE to improve our state management and back pressure. Both of these resources mention ensuring objects used in the flow are valid POJOs to