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

["stephen mallette (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TINKERPOP-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760953#comment-16760953 ] 

stephen mallette commented on TINKERPOP-2151:
---------------------------------------------

No language variant provides properties except for Java which has always been a source of confusion. As a first step toward resolving that for 3.4.0, the decision was made to include {{ReferenceElementStrategy}} which is installed by default in Gremlin Server to detach elements without properties automatically so that the behavior is consistent across all languages including Java. It's just not a good practice to return all properties of an element, anymore than it is a good practice to write {{SELECT * FROM table}}.

> As mentioned else where, using `valuesMap` isn't an ideal solution due to the lack of `inV` and `outV` in the edges.

that's a good point. perhaps {{valueMap().with(WithOptions.tokens)}} should be extended a bit for edges somehow [~dkuppitz] ?

> 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
>            Priority: Minor
>
> 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)