Florian Hockmann created TINKERPOP-1927:
-------------------------------------------
Summary: Gherkin scenario expects list with duplicates, but
receives g:Set
Key: TINKERPOP-1927
URL: https://issues.apache.org/jira/browse/TINKERPOP-1927
Project: TinkerPop
Issue Type: Bug
Components: dotnet, javascript, python, test-suite
Affects Versions: 3.3.1
Reporter: Florian Hockmann
The scenario
{{g_V_storeXaX_byXoutEXcreatedX_countX_out_out_storeXaX_byXinEXcreatedX_weight_sumX}}
expects
{code:java}
| result |
| d[1].l |
| d[1].l |
| d[0].l |
| d[0].l |
| d[0].l |
| d[2].l |
| d[1.0].d |
| d[1.0].d |
{code}
but we receive this from the server:
{code:java}
{
"@type": "g:Set",
"@value": [
{
"@type": "g:Int64",
"@value": 1
},
{
"@type": "g:Int64",
"@value": 1
},
{
"@type": "g:Int64",
"@value": 0
},
{
"@type": "g:Int64",
"@value": 0
},
{
"@type": "g:Int64",
"@value": 0
},
{
"@type": "g:Int64",
"@value": 2
},
{
"@type": "g:Double",
"@value": 1
},
{
"@type": "g:Double",
"@value": 1
}
]
}
{code}
The set returned by the server contains 4 duplicates that shouldn't be part of
the expected result in the scenario.
Unfortunately, while working on TINKERPOP-1865 we noticed that gremlin-python
and gremlin-javascript fail when the scenario is fixed like that. So those two
GLVs probably need to be fixed to handle {{g:Set}} correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
