[PHOENIX-2324] Decimal data sent by Avatica cannot be interpreted by some clients

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Invalid
• Affects Version/s: 4.5.2
• Labels: avatica calcite decimal double json number phoenix queryserver wireprotocol
• Assignee: Unassigned
• Reporter: Kevin Liew
• Created: 15/Oct/15 16:56
• Updated: 16/Nov/15 20:43
• Resolved: 14/Nov/15 02:01

Description

JSON specifies a 'number' data type which does not differentiate between integer and floating-point values. The encoding for JSON numbers is implementation-specific. 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. If it is sent as a number, we cannot be expect that all JSON-spec compliant library will handle it properly.

ie. Phoenix sends a decimal as a JSON number, but Rapidjson can only extract JSON numbers as integer or double because the C++ language does not have native decimal support.