stephen mallette closed TINKERPOP-1918.
    Resolution: Fixed
      Assignee: stephen mallette

Thanks for identifying the root of the problem - not sure why i didn't see that 
myself - anyway - fixed via CTR with:


> 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

Reply via email to