It's not an error. It's just a bit of information from the type
extractor; it still analyzes the type to check whether it is a POJO,
because if it was then it wouldn't need to use Kryo.
IOW, unless you experience issues with running your job, you can safely
ignore it.
On 6/21/2021 9:11 PM, Debraj Manna wrote:
Hi
As mentioned in the documentation
<https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/dev/serialization/custom_serializers/>
I have registered the Protobuf Serializer like below
env.getConfig().registerTypeWithKryoSerializer(SelfDescribingMessageDO.class,
ProtobufSerializer.class);
It is working but I am seeing INFO logs like below
2021-06-16 06:17:22,235 INFO org.apache.flink.api.java.typeutils.TypeExtractor
-class com.vnera.model.protobufs.SelfDescribingMessageDO does not
contain a getterfor field bitField0_
2021-06-16 06:17:22,235 INFO org.apache.flink.api.java.typeutils.TypeExtractor
-class com.vnera.model.protobufs.SelfDescribingMessageDO does not
contain a setterfor field bitField0_
Can someone let me know why am I seeing this and how can I get around
this?
Flink Version 1.13.0
