[
https://issues.apache.org/jira/browse/TINKERPOP3-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15013884#comment-15013884
]
stephen mallette edited comment on TINKERPOP3-978 at 11/19/15 5:03 PM:
-----------------------------------------------------------------------
it needs to be edge list as that is easier to deal with than adjacency list for
non-jvm folk and it will deserialize without a cache which is required on
adjacency list since we don't store vertex labels with edges. not much else we
can do with this i don't think. just trying to get symmetry between graphson
and gryo on this ticket.
was (Author: spmallette):
it needs to be edge list as that is easier to deal with than adjacency list for
non-jvm folk. not much else we can do with this i don't think. just trying to
get symmetry between graphson and gryo on this ticket.
> Native TinkerGraph Serializers for GraphSON
> -------------------------------------------
>
> Key: TINKERPOP3-978
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-978
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: tinkergraph
> Affects Versions: 3.0.2-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Minor
> Fix For: 3.1.1-incubating
>
>
> TinkerGraph supports native serialization to Gryo, meaning that you can pass
> a TinkerGraph directly to a Kryo object and have it serialize it - which
> means that it can be treated as a return object from Gremlin Server (which is
> nice for subgraphs).
> Add the same capability for GraphSON so that non-jvm languages can take
> advantage of that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
