[
https://issues.apache.org/jira/browse/TINKERPOP-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410524#comment-16410524
]
ASF GitHub Bot commented on TINKERPOP-1909:
-------------------------------------------
GitHub user ashwini-ms opened a pull request:
https://github.com/apache/tinkerpop/pull/824
Uniform object model for GraphSON response for client drivers
Based on the discussion here:
[](https://issues.apache.org/jira/browse/TINKERPOP-1909)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashwini-ms/tinkerpop master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tinkerpop/pull/824.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #824
----
commit ba915458a3d4121a55d563dfc8267417574c8f94
Author: Ashwini Singh <30875507+ashwini-ms@...>
Date: 2018-03-22T22:42:43Z
update index.asciidoc
Add design doc for reference based object model
commit 79dc2cdf157a4df688a68f80100e6aecefcc28b9
Author: Ashwini Singh <30875507+ashwini-ms@...>
Date: 2018-03-22T22:43:44Z
fix format
fixing format
----
> 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)
