Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/304#issuecomment-70527831
My point is that we cannot make all types anyone would ever use work out of
the box. Any sample of types that work out of the box is incomplete and sort of
arbitrary and we have to be careful not to trash the Kryo instances by
overloading them with pre-registered serializers. Registering default
serializers is actually a bit inefficient (array list with move operations).
I thought that having a util that you can call to register serializers for
a certain lib/topic would make things transparent, easy for the user, and keep
kryo "slim" initially.
BTW: We may actually start thinking about Kryo pooling, if we want to add
vastly more default serializers.
---
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.
---
