[CALCITE-796] Avatica remote service truncates java.sql.Timestamp to milliseconds

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Lukas Lalinsky
• Created: 12/Jul/15 13:22
• Updated: 22/Feb/19 01:20

Description

TypedValue in Avatica read/writes java.sql.Timestamp in milliseconds even though natively the type supports nanosecond precision (and Phoenix does use the full precision). The JSON serialization protocol should count with this.

I'd suggest serializing java.sql.Timestamp with `toString()` and deserializing with `valueOf()` if it's a string. Alternatively, it could be stored as a decimal number or just total number of nanoseconds.