[
https://issues.apache.org/jira/browse/TINKERPOP-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406231#comment-16406231
]
ASF GitHub Bot commented on TINKERPOP-1865:
-------------------------------------------
Github user FlorianHockmann commented on the issue:
https://github.com/apache/tinkerpop/pull/820
> Also, I've switched to use a lambda (now that we support it :) ) to
obtain all the edges for the scenario data,
That lambda really makes the traversal much easier to read and understand :)
For
`g_V_storeXaX_byXoutEXcreatedX_countX_out_out_storeXaX_byXinEXcreatedX_weight_sumX`,
I'd say that we should change the scenario to only expect the 4 unique
values and then fix gremlin-python and gremlin-javascript as they seem to
deserialize sets incorrectly at the moment. (Otherwise they had to fail for
this test at the moment.) But I'm not sure if we want to do all that in this PR.
> @FlorianHockmann I hope you don't mind that I've directly pushed to the
dev branch, feel free to revert the commits if needed.
Certainly not, thanks for helping me with this PR!
> Run Gremlin .NET GLV tests with GraphSON 3.0
> --------------------------------------------
>
> Key: TINKERPOP-1865
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1865
> Project: TinkerPop
> Issue Type: Improvement
> Components: dotnet
> Affects Versions: 3.3.1
> Reporter: stephen mallette
> Assignee: Jorge Bay
> Priority: Major
> Fix For: 3.3.2
>
>
> GLV tests currently run for GraphSON 2.0 with .NET - they should be running
> for 3.0 especially on the 3.3.x line of code. Ideally we should probably run
> tests for both versions, but perhaps that is a separate issue at this point
> as it is for Python on TINKERPOP-1864
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
