[
https://issues.apache.org/jira/browse/TINKERPOP-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395192#comment-16395192
]
Florian Hockmann commented on TINKERPOP-1918:
---------------------------------------------
Thanks, I wasn't 100% sure that it needed to be changed in the feature files as
the other GLVs didn't have this problem, but that's probably just because
Python and Javascript are not type-safe (and I assume that Java and Groovy
don't use the features yet).
> Scenarios fail because of wrong numerical types
> -----------------------------------------------
>
> Key: TINKERPOP-1918
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1918
> Project: TinkerPop
> Issue Type: Bug
> Components: dotnet, test-suite
> Affects Versions: 3.2.7
> Reporter: Florian Hockmann
> Assignee: stephen mallette
> Priority: Major
> Fix For: 3.2.8, 3.3.2
>
>
> Two scenarios currently fail for Gremlin.Net because the types returned by
> the server don't match the expected ones:
> *
> {{g_withSackX1_sumX_VX1X_localXoutXknowsX_barrierXnormSackXX_inXknowsX_barrier_sack}}
> expects results as {{double}}, but we receive {{gx:BigDecimal}} from the
> server which gets deserialized to the .NET type {{decimal}}.
> * {{g_withBulkXfalseX_withSackX1_sumX_V_out_barrier_sack}} expects results
> as {{double}}, but we receive {{g:Int32}} from the server which gets
> deserialized to {{int}}.
> I'm not sure whether those are actually bugs in Gremlin.Net or if the
> specified types in the scenarios are simply wrong as there doesn't seem to be
> much we can do in .NET to get the types correctly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
