Github user okram commented on the issue:
https://github.com/apache/incubator-tinkerpop/pull/325
So yea... sorta feels like we are where we were before in a way. And yea,
all that Input, Output, Kryo stuff is what causes all the problems.
So now I'm wondering, why not just register the requisite classes with
`GryoSerializer`? Yes, we miss one every now and then, but we add it. Sooner or
later they will all be there. Moreover, if a person needs it now, they can just
register it with `GryoMapper`. Did you try just registering your "high density
map" w/ `GryoSerializer`?
I know that last paragraph sucks given all the work you did, but having two
ways of doing something and one way being Spark-specific doesn't make me happy
and this is why `GryoSerializer` came into being..........
---
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.
---
