Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-57572019
I think it's better to do both and explain that there might be problems.
Otherwise users will see this new API and perhaps be surprised that their old
registrator is no longer called. Not everyone reads the docs on the new API, so
they might never notice, and just get poor performance.
BTW looking at Kryo's docs, it does support multiple register calls on the
same class, and it just uses the value from the last one. So it will probably
do the right thing here if we call their custom registrator last.
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
