Github user okram commented on the issue:
https://github.com/apache/incubator-tinkerpop/pull/325
@dalaro
> The problem with custom registrations is that GryoMapper allows the user
to provide a serializer written against shaded Kryo. This is not compatible
with Spark's KryoSerializer. I don't see a way to make it compatible without
putting fake org.apache.tinkerpop.shaded.kryo.* classes on the classpath, which
could get pretty ugly.
Yea, thats a problem and the reason why `GryoSerializer` exists. We don't
want to make `SparkGraphComputer` "special." Users register their serializers
with `Graph` and all OLTP and OLAP systems take it from there. If, for
`SparkGraphComputer`, they ALSO have to register them with Spark, that is no
bueno. Is there a way to create "proxies" that map between shaded and unshaded
Kryo so that registered `GryoMapper` serializers can be used as unshaded Kryo
serializers by Spark?
---
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.
---
