Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/18343
True. I guess since the same serializer instance is not reused, you don't
get the benefits of the optimizations that don't require sending the class name
after it first shows up..
But back to the change, it feels like the correct thing would be to
implement `KryoSerializable` here to minimize the size of the serialized data
when using kryo too. Although maybe that's not too much gain given the class is
already registered in `KryoSerializer`?
---
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]
