[CALCITE-5552] Returned timestamp is incorrect after the 100th row

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: avatica-1.23.0
• Component/s: avatica
• Assignee: Unassigned
• Reporter: Magnus Mogren
• Created: 02/Mar/23 16:01
• Updated: 28/Feb/24 06:03

Description

When fetching data that contains timestamps the returned timestamp after row 100 is incorrect.

This can be reproduced using the CSV adapter (calcite-csv) using the TSTAMPS.csv file attached. It contains 101 timestamps with the value 1900-01-01 00:00:00. The first 100 is returned correctly, but number 101 in the result has the value 1899-12-31 23:00:00 instead.

Marking this bug as critical since not beeing able to trust the values returned by calcite is as bad as it gets in my opinion.

I do not know if the bug is in calcite or avatica.

I have created a project that reproduces the issue. You can find that here: nytro77/calcite-timestamp-bug: Showcase bug in Calcite or Avatica that causes faulty timestamps to be returned (github.com)

It starts an AvaticaServer that serves the attached file as a table using calcite-csv and a unit tests that connects to the server and fetches the data.
Run it with 

./mvnw test

Issue Links

• is duplicated by: CALCITE-4120 Inconsistent Calendar used In JdbcMeta between prepareAndExecute and Fetch