You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Jorge Bay (JIRA)" <ji...@apache.org> on 2018/09/05 13:59:00 UTC

[jira] [Commented] (TINKERPOP-1942) Binary serialization format

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

Jorge Bay commented on TINKERPOP-1942:
--------------------------------------

GraphSON3 handles null values by hiding type information, instead of:

{code}
{ @type: "g:MyTypeName", @value: null }
{code}

GraphSON deserialization returns

{code}
null
{code}

This issue makes creating complex types, with nested subtypes, in GraphSON much harder. Introducing a new format is a good opportunity to fix this issue, focusing on making easier to serialize/deserialize complex object types.

> Binary serialization format
> ---------------------------
>
>                 Key: TINKERPOP-1942
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1942
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: io
>            Reporter: Jorge Bay
>            Priority: Major
>
> We should provide a binary serialization format designed to reduce serialization overhead and minimizing the size of the payload that is transmitted over the wire.
> It could be implemented in a very similar way as Kryo support but with interoperability in mind and ultimately we could fade Gryo out, as now with the GLVs it doesn't have a role to play.
> The main benefit would be the performance improvement, making serialization and deserialization processing time negligible on both the server and the client.
> Background: https://lists.apache.org/thread.html/13e70235591853801bab16ed457ee4f56f3dfe2d1c5817c34a036408@%3Cdev.tinkerpop.apache.org%3E



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)