You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/01/30 00:29:39 UTC
[jira] [Created] (TINKERPOP-1111) Gryo and nested objects not
serializing using GryoSerializers
Marko A. Rodriguez created TINKERPOP-1111:
---------------------------------------------
Summary: Gryo and nested objects not serializing using GryoSerializers
Key: TINKERPOP-1111
URL: https://issues.apache.org/jira/browse/TINKERPOP-1111
Project: TinkerPop
Issue Type: Improvement
Components: structure
Affects Versions: 3.1.1-incubating
Reporter: Marko A. Rodriguez
If you have a {{HashMap}} filled with objects that are Kryo serializable (that is, the objects have a registered {{Serializer}}), it will try and serialize them as Java serialization objects.
I believe this is because of {{add(Triplet.<Class, Function<Kryo, Serializer>, Integer>with(HashMap.class, null, 11));}} means use {{JavaSerializer}} and thus, Kryo serialization ends there. ?? .... :|
I'm noticing this when I have a {{HashMap}} full of {{ComputerVertex}} objects which implement {{Vertex}}, but I'm get a "ComputerVertex not serializable exception" when it should be converted to a {{DetachedVertex}} and serialized. ???
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)