Hi Alex, have you had a look at TypeInfoFactory? That might be the best way to come up with a custom serialization mechanism. See the docs [1] for further details.
Best, Matthias [1] https://ci.apache.org/projects/flink/flink-docs-master/docs/dev/datastream/fault-tolerance/serialization/types_serialization/#defining-type-information-using-a-factory On Tue, Sep 14, 2021 at 8:33 PM Alex Cruise <a...@cluonflux.com> wrote: > Hi there, > > I appreciate the fact that Flink has built-in support for making POJO and > Scala `case class` serialization faster, but in my project we use immutable > Kotlin `data class`es (analogous to Scala `case class`es) extensively, and > we'd really prefer not to make them POJOs, mostly for style/taste reasons > (e.g. need a default constructor and setters, both are anathema!) > > Does anyone know of a good way for us to keep using idiomatic, immutable > Kotlin data classes, but to get much faster serialization performance in > Flink? > > Thanks! > > -0xe1a >
