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

Ashwini Singh commented on TINKERPOP-1909:
------------------------------------------

 

Few more questions. 

I understand the future direction for TinkerPop 4.X. But as of now what do you 
think about filling the gaps between .net and other drivers in TInkerPop3.X for 
customers who have taken the dependency on the older version?

What is our plan for bulk insert story (data insert) on TinkerPop 4.X? For a 
query, it makes sense to return reference data for different reasons(perf 
etc.). But, what is our plan for reading data from full graphSON file and 
insert into the store?, Without the full object model.  

> 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)

Reply via email to