[CALCITE-795] Loss of precision when sending a decimal number via the remote JSON service

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0-incubating
• Flags: Patch
• Assignee: Julian Hyde
• Reporter: Lukas Lalinsky
• Created: 12/Jul/15 12:12
• Updated: 01/Sep/15 03:02
• Resolved: 16/Jul/15 18:55

Description

When sending for example

{"type":"NUMBER","value":"333.333"}

to the "fetch" request of the remote JSON service, the exact value will not be kept and after one UPSERT/SELECT roundtrip in Phoenix I will get 333.332 back.

Interestingly enough, this worked in Calcite 1.2 before the TypedValue class was introduced, but I think that was working just by accident.

The attached patch changes the Jackson object mapper to decode any JSON float to BigDecimal, unless the code explicitly asks for Float/Double. I think that shouldn't break anything and it solves this problem.