You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Daniel Kuppitz (JIRA)" <ji...@apache.org> on 2016/12/09 14:05:58 UTC
[jira] [Commented] (TINKERPOP-1574) Get rid of untyped GraphSON 2.0
[ https://issues.apache.org/jira/browse/TINKERPOP-1574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15735408#comment-15735408 ]
Daniel Kuppitz commented on TINKERPOP-1574:
-------------------------------------------
A specific problem popped up recently: I was using {{constant(Collections.emptySet())}} in a traversal which was causing errors, because the serialized {{Set}} was deserialized as a {{List}} (for untyped GraphSON all implementations of {{Collection}} look the same and thus every {{Collection}} is considered to be a {{List}}). A workaround has been added in this commit: https://github.com/apache/tinkerpop/commit/69b314cb2e52f33dbab29d3cddaadacb4ec69099
I think, once the GraphSON issue is fixed, the workaround should be reverted as it seems to be a good extra test case.
> Get rid of untyped GraphSON 2.0
> -------------------------------
>
> Key: TINKERPOP-1574
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1574
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Affects Versions: 3.2.3
> Reporter: Marko A. Rodriguez
> Labels: breaking
> Fix For: 3.3.0
>
>
> We should not have GraphSON 2.0 untyped. Too many degrees of freedom. GraphSON should be GraphSON typed and thats that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)