Hi,
Have you looked at [1]?
You can annotate your type and provide a type info factory. The factory
would be used to create the TypeInformation for that type, and in turn
create the serializer used for that type.
[1]
https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/types_serializat
Hi,
I am using Avro GenericRecord for most of IN/OUT types from my custom
functions. What I have noticed is that default Avro GenericRecord
serializer, also serializes Schema which makes messages very heavy and
hence impacts overall performance. In my case I already know the schema
before hand and