Hi, What that LOG means (i.e. "must be processed as a Generic Type") is that Flink will have to fallback to using Kryo for the serialization for that type.
You should be concerned about that if: 1) That type is being used for some persisted state in snapshots. That would be the case if you've registered state of that type, or is used as the input for some built-in operator that persists input records in state (e.g. window operators). Kryo generally does not have a friendly schema evolution story, so you would want to avoid that going into production. 2) Kryo itself is not the fastest compared to Flink's POJO serializer, so that would be something to consider as well even if the type is only used for transient, on-wire data. I think in your case, since your POJO contains an inner field that cannot be recognized as a POJO (i.e. the LocalDateTime), then your outer class is also not recognized as a POJO. BR, Gordon -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
