[jira] [Comment Edited] (TINKERPOP-1844) Python GLV test should run for GraphSON 3.0

["stephen mallette (JIRA)" <ji...@apache.org>]

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

stephen mallette edited comment on TINKERPOP-1844 at 1/4/18 12:17 AM:
----------------------------------------------------------------------

This problem seems to be related to the use of {{Set}} (at least for the first failing test I came across. This traversal:presents the problem:

{code}
gremlin> g.V().store("a").by(__.outE("created").count()).out().out().store("a").by(__.inE("created").values("weight").sum()).cap("a")
==>[1,1,0,0,0,2,1.0,1.0]
{code}

the above is a {{Set}} in java, but a python {{Set}} does not distinguish between long/double/int/etc: the way java does so we instead get a set of {{[0,1,2]}}. Not sure what we do with that. [~davebshow] any ideas?






was (Author: spmallette):
This problem seems to be related to the use of {{Set}} (at least for the first failing test I came across. This traversal:presents the problem:

{code}
gremlin> g.V().store("a").by(__.outE("created").count()).out().out().store("a").by(__.inE("created").values("weight").sum()).cap("a")
==>[1,1,0,0,0,2,1.0,1.0]
{code}

the above is a {{Set}} in java, but a python {{Set}} does not distinguish between long/double/int/etc: the way java does so we instead get a set if {{[0,1,2]}}. Not sure what we do with that. [~davebshow] any ideas?





> Python GLV test should run for GraphSON 3.0
> -------------------------------------------
>
>                 Key: TINKERPOP-1844
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1844
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python
>    Affects Versions: 3.3.0
>            Reporter: stephen mallette
>            Priority: Critical
>
> The GLV tests are running for python on GraphSON 2.0. When I ran them for GraphSON 3.0 I received some strange errors that looked like they might have been related to bulking, but I can't say for sure. Anyway, we should definitely be running these tests against 3.0 and potentially 2.0 as well (2.0 can be a separate ticket and is less of a priority).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)