[
https://issues.apache.org/jira/browse/TINKERPOP-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17873291#comment-17873291
]
Ken Hu commented on TINKERPOP-2363:
-----------------------------------
This opens a wider discussion about how we want to handle coercion for drivers
in languages that have a single numeric type. Maybe we should do something
similar as what was done in TINKERPOP-2360 but extend it to the rest of the
numeric types.
In any case, since GraphBinary is now the default (and in the future maybe the
only) serializer for the GLVs, I'm going to increase the priority of this
ticket.
> GraphBinary and numerics for Python
> -----------------------------------
>
> Key: TINKERPOP-2363
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2363
> Project: TinkerPop
> Issue Type: Improvement
> Components: python
> Affects Versions: 3.4.6
> Reporter: Stephen Mallette
> Priority: Major
>
> After TINKERPOP-2360 we've started down the path of coercing python numerics
> to Java type ranges. GraphBinary doesn't do that and therefore switching
> serializers from GraphSON to GraphBinary will have the potential to result in
> error if the python numeric overflows the Java integer space. In addition, we
> don't support {{BigInteger}} serialization apparently so that remains a
> problem. This ticket should just sort out GraphBinary and numbers all at once.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
