Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/236#issuecomment-72433217
Yes, it is not a good solution But what you propose isn't either: If we use
Kryo for those subclasses that we cannot handle then nothing works anymore. The
whole reason we have support for POJOs is that we can theoretically compare
them in their binary representation. We are not doing this right now (the
PojoComparator is always comparing in deserialised form) but we added it with
that goal in mind.
If we don't want to do that anymore we can just get rid of the whole POJO
serialisation code and use Kryo for everything.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
