Github user dalaro commented on the issue:
https://github.com/apache/incubator-tinkerpop/pull/325
The problem is that GryoSerializer doesn't actually work. This is not the
first time it has shown behavior on Spark or scala runtime classes which
diverges from the behavior of Spark's KryoSerializer/JavaSerializer.
I realize that asking users to write custom serializers against the shim
(to be compatible with everything) in the long term or to duplicate
registrations in the short term (if they want to use Gryo in one place and
Spark graph computation in another, using the same custom types) is not ideal,
but I think the status quo is even worse.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
