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

Kevin Liew updated PHOENIX-2324:
--------------------------------
    Description: 
JSON specifies a 'number' data type which does not differentiate between 
integer and floating-point values. Libraries such as RapidJSON can treat all 
non-integer values as 'double' while still being compliant with JSON 
specifications. As a result, decimal values sent by Phoenix  will lose 
precision on the client side. 

Decimal data should be sent as a string to adhere with JSON specifications. If 
it is sent as a number, it cannot be expected that any JSON-spec compliant 
library will handle it properly. 

This also affects float type data

  was:
JSON specifies a 'number' data type which does not differentiate between 
integer and floating-point values. Libraries such as RapidJSON can treat all 
non-integer values as 'double' while still being compliant with JSON 
specifications. As a result, decimal values sent by Phoenix  will lose 
precision on the client side. 

Decimal data should be sent as a string to adhere with JSON specifications. If 
it is sent as a number, it cannot be expected that any JSON-spec compliant 
library will handle it properly. 


> Decimal data sent by Avatica does not adhere to JSON specs
> ----------------------------------------------------------
>
>                 Key: PHOENIX-2324
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2324
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.5.2
>            Reporter: Kevin Liew
>              Labels: avatica, calcite, decimal, double, json, number, 
> phoenix, queryserver, wireprotocol
>
> JSON specifies a 'number' data type which does not differentiate between 
> integer and floating-point values. Libraries such as RapidJSON can treat all 
> non-integer values as 'double' while still being compliant with JSON 
> specifications. As a result, decimal values sent by Phoenix  will lose 
> precision on the client side. 
> Decimal data should be sent as a string to adhere with JSON specifications. 
> If it is sent as a number, it cannot be expected that any JSON-spec compliant 
> library will handle it properly. 
> This also affects float type data



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to