Hi Alexis Flink will recognize the POJO class and use PojoTypeInfo to serialize and deserialize it. For specific constraints on POJO classes, please refer to [1].
Users can also define serialization methods for their own classes, as you mentioned in the email [1] https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/api/java/typeutils/PojoTypeInfo.java Best, Shammon FY On Wed, Apr 12, 2023 at 1:15 AM Alexis Sarda-Espinosa < sarda.espin...@gmail.com> wrote: > Hello, > > according to the documentation, a POJO must have a no-arg constructor and > either public fields or public getters and setters with conventional > naming. I recently realized that if I create an explicit TypeInfoFactory > that provides Types.POJO and all other required details, the getters and > setters aren't needed. Is this an official feature? > > I ask because this means some classes could have an "immutable contract", > so to speak. I'm guessing final fields might still be unsupported, but I > haven't validated. > > Regards, > Alexis. > >
