[CALCITE-2243] Timestamp values change with remote connection when the result set size exceeds 100 rows

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.16.0
• Component/s: core
• Assignee: Unassigned
• Reporter: Markku Vuorenmaa
• Created: 09/Apr/18 11:31
• Updated: 22/Feb/19 01:22

Description

Table queries with TIMESTAMP values return incorrect values when the result set size is larger than 100 rows. Perhaps the timezone shift is calculated twice, as the first 100 lines are correct and the bug always occurs after that. The default fetch size in the code seems to be 100. The bug should be reproducable by running the attached code, which the same model with local and remote connection and gets a different data as a result.

Some output shortly:

Local:

#1 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#2 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#100 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#101 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#102 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#200 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38

Remote:

#1 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#2 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#100 TIME=2018-04-09 11:20:38.31; FORMATTED=9.4.2018 14:20:38
#101 TIME=2018-04-09 08:20:38.31; FORMATTED=9.4.2018 14:20:38
#102 TIME=2018-04-09 08:20:38.31; FORMATTED=9.4.2018 14:20:38
#200 TIME=2018-04-09 08:20:38.31; FORMATTED=9.4.2018 14:20:38

TimestampsIssue.java