You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Stephen Mallette (Jira)" <ji...@apache.org> on 2022/04/13 10:27:00 UTC

[jira] [Assigned] (TINKERPOP-2156) GraphSON BigInteger and BigDecimal should use strings

     [ https://issues.apache.org/jira/browse/TINKERPOP-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette reassigned TINKERPOP-2156:
-------------------------------------------

    Assignee:     (was: Stephen Mallette)

> GraphSON BigInteger and BigDecimal should use strings
> -----------------------------------------------------
>
>                 Key: TINKERPOP-2156
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2156
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 3.3.5
>            Reporter: Stephen Mallette
>            Priority: Major
>              Labels: breaking
>
> Both {{BigDecimal}} and {{BigInteger}} serialize to JSON numeric as follows:
> {code}
> {
>   "@type" : "gx:BigDecimal",
>   "@value" : 123456789987654321123456789987654321
> }
> {code}
> but should probably serialize to a string value instead. Jackson 2.10 should support that option and make it easier for other language variants to handle. Interestingly Jackson 2.9.8 which we are currently on seems to support the consumption of either number or string so it seems likely that this can be done without a significant breaking change. From the point we implement this we can simply say that going forward we will prefer support of a string value. 
> As this change would still be breaking to those who consume raw graphson or something, the "breaking" label is added to this ticket.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)