[
https://issues.apache.org/jira/browse/TINKERPOP-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384956#comment-16384956
]
Ashwini Singh commented on TINKERPOP-1909:
------------------------------------------
I agree with the direction of gremlin towards being more tidy about data
communicated between client and server and we should be wary of the performance
problems with always dealing with multi-properties. But, I still think it would
be worth consider our ability to de-serialize full vertex/edges if needed.There
are few options we can consider for future in TinkerPop 4.x.
# Using output format, a Gremlin Server configuration. Output format can be
Ref (return id and label) or GraphSONCompact (Ref+ properties) or
GraphSON(Ref+properties+ edges). And, Default to Ref. This provides client
ability to retrieve more details if required and avoid multiple query. And,
fully controlled by the client.
# We go ahead with the current ref based object model and let applications
extend the object model + deserializers if required. Looks doable for
Gremlin.Net at least.
What do you think ?
> Gremlin.Net does not have complete object model as compared to other client
> drivers and unable to de-serialize properties for vertex/edge graphSON.
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TINKERPOP-1909
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1909
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet
> Affects Versions: 3.3.1
> Reporter: Ashwini Singh
> Priority: Major
>
> Looks like the object model for Gremlin.Net client driver is not as par with
> Java driver. We cannot deserialize a GraphSON response to tinkerpop object
> completely. For example, Gremlin.Net object model cannot deserialize
> properties from a graphSON response object (vertex/edges). Currently, we only
> deserialize id and label field from a vertex/edge graphSON.
>
> So, to desterilize the object model, users have to write a custom
> deserialization code and create the object. The current de-serializers (for
> vertex/edge) will strip off details like properties.
>
> I am filing it as a bug but it could fall into improvement as well.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
