Skip to content

Fix: improve error messages for non-SQLException Java exceptions (legacy #250) #80

@HenryNebula

Description

@HenryNebula

Description

When a JDBC driver throws a non-SQLException (e.g., RuntimeException), the error message propagated to Python users is uninformative. Our _handle_sql_exception_jpype() wraps these as InterfaceError but does not extract the Java exception cause chain, leaving users with just a generic "Java Exception" message.

This was reported when long Presto queries failed with a 502 Bad Gateway wrapped in a RuntimeException, but the user could not determine the root cause from the error message.

Legacy issue: baztian/jaydebeapi#250

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions