Re: Re: pojo warning when using auto generated protobuf class

2021-04-26 Thread Yun Gao
tasks resides, and use jmap to see if ProtoSerializer is created or not. Best, Yun --Original Mail -- Sender:Prashant Deva Send Date:Sun Apr 25 01:18:41 2021 Recipients:Yun Gao CC:User Subject:Re: pojo warning when using auto generated protobuf class so i

Re: pojo warning when using auto generated protobuf class

2021-04-24 Thread Prashant Deva
ts/flink/flink-docs-stable/dev/custom_serializers.html > ) > > > >> --Original Mail -- >> *Sender:* Prashant Deva < prashant@ astradot. com ( prash...@astradot.com ) >> > >> *Send Date:* Sat Apr 24 11:00:17 2021 >> *Recipients:* Us

Re: pojo warning when using auto generated protobuf class

2021-04-24 Thread Yun Gao
Hi Prashant, I think the warn is given when calling return TypeInformation.of(Trace.APITrace::class.java) Currently flink does not have the native support for the protobuf types yet[1], thus it would use a generic serializer created by kryo. This should not affect the rightness of the progra

pojo warning when using auto generated protobuf class

2021-04-23 Thread Prashant Deva
I am seeing this warning msg when trying to use a custom protobuf de/serializer with kafka source with auto generated java protobuf class: 18:41:31.164 [main] INFO org.apache.flink.api.java.typeutils.TypeExtractor - Class class com.xx.APITrace cannot be used as a POJO type because not all fields a