Skip to content

Unimplemented error when the output table contains timestamp with timezone #787

Closed

Description

@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):

Image

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

Image

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.

Activity

  1. lidavidm commented on Jun 13, 2025

    @lidavidm
    Member

    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.

  2. Ke-Wng commented on Jun 13, 2025

    @Ke-Wng
    Author

    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.

    Image

  3. Ke-Wng commented on Jun 13, 2025

    @Ke-Wng
    Author

    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.

    Image

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

    Image

  4. lidavidm commented on Jun 13, 2025

    @lidavidm
    Member

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

  5. Ke-Wng commented on Jun 16, 2025

    @Ke-Wng
    Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type: bugSomething isn't workinghelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions