You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Matthew Stafford (JIRA)" <ji...@apache.org> on 2019/02/05 15:36:00 UTC

[jira] [Created] (TINKERPOP-2151) Support for Vertex and Edge property deserialization in Python GLV

Matthew Stafford created TINKERPOP-2151:
-------------------------------------------

             Summary: Support for Vertex and Edge property deserialization in Python GLV
                 Key: TINKERPOP-2151
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2151
             Project: TinkerPop
          Issue Type: Improvement
          Components: python
    Affects Versions: 3.3.5
            Reporter: Matthew Stafford


It seems that the GraphSON serialization in the Python GLV differs from other GLVs (I've checked JavaScript and assuming Java as well) in that it doesn't deserialize Vertex and Edge properties. I've found a few discussions of this (TINKERPOP-1474, TINKERPOP-1565) but it doesn't seem there was a clear resolution to whether this was something that'd be addressed in the 3.3.x series or if things would be left with a lack of parity across GLVs and a different solution was approached in the 3.4.x series.

As mentioned else where, using `valuesMap` isn't an ideal solution due to the lack of `inV` and `outV` in the edges. Since this was never quite resolved, does it make sense for me to go in and make the changes to the GraphSON serializers?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)