Ashwini Singh commented on TINKERPOP-1909:

Yes, agree to keep this discussion only for 3.X


Extending the object model+ de-serialiser could be a temporary solution that we 
have suggested to some of our clients or provided change ourselves. But, its 
not a scalable solution for long term. So , we would prefer to the Java and 
dotnet(+other drivers) to adhere to the same object model for version 3.X. [We 
can definitely move to new model going forward to TinkerPop4+]. And, to me it 
makes sense to keep all the drivers aligned to same model in the same major 
version. Can we scope this fix only for 3.X client drivers, 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

Reply via email to