Unimplemented error when the output table contains timestamp with timezone

[Ke-Wng]

Describe the bug, including details regarding any error messages, version, and platform.

Description

When we create a table with the following schema (the ts column is a timestamp with a time zone)：

Then we query this table, its output will report unimplemented error:

But if we change the flight sql jdbc driver from 18.3.0 to 18.2.0 or earlier, the ouput is just fine.

Plantform

• Client: DBeaver Community Edition 25.1.0
• Operating System: Windows 10 19045.5965
• Database: datalayers (our proprietary database)
• Driver: flight-sql-jdbc-driver 18.3.0

Potential reasons

The error messages suggest the issue stems from Arrow-Java 18.3.0 is dependent on Calcite-Avatica 1.26.0. It appears Calcite-Avatica 1.26.0 doesn't support timestamp types with timezone in query result sets. In contrast, Arrow-Java 18.2.0 and earlier versions rely on Calcite-Avatica 1.25.0 (as seen in #634), which explains why their query result sets are correct.

[lidavidm]

Are you sure this is a regression? It appears getObject is in the traceback so this will depend on what type exactly your client/DBeaver is requesting.

[Ke-Wng]

Are you sure this is a regression? It appears getObject is in the traceback so this will depend on what type exactly your client/DBeaver is requesting.

However, if we downgrade the Flight SQL JDBC driver from 18.3.0 to 18.2.0, while keeping the table schema, DBeaver and our database unchanged, the output becomes correct.

[Ke-Wng]

Are you sure this is a regression? It appears getObject is in the traceback so this will depend on what type exactly your client/DBeaver is requesting.

However, if we downgrade the Flight SQL JDBC driver from 18.3.0 to 18.2.0, while keeping the table schema, DBeaver and our database unchanged, the output becomes correct.

After downgrading the JDBC driver, the table's schema (as shown in DBeaver) will reflect a timestamp type, without timezone information.

[lidavidm]

I think it's more likely #464 but I don't have the time to confirm.

[Ke-Wng]

The issue has been resolved in dbeaver/dbeaver#38381. Thanks for your support!