Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Investigate Error Handling for unhandled SQL query #499

Open
birschick-bq opened this issue Feb 1, 2023 · 0 comments
Open

[BUG] Investigate Error Handling for unhandled SQL query #499

birschick-bq opened this issue Feb 1, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@birschick-bq
Copy link
Contributor

Environment

  • DocumentDB JDBC driver version: 1.4.4
  • DocumentDB server version: n/a
  • OS: [e.g. MacOS Big Sur 11.5.1, Windows 10 64-bit] n/a
  • BI Tool or client name: n/a
  • BI Tool or client version: n/a
  • Java version (if known): n/a

Problem Description

  1. Steps to reproduce:
    • In DocumentDbQueryMappingService original exceptions can be hidden on call to getExceptionMessages(e) - for example, if it throws a null pointer exception, hiding the original exception. This should be adjusted to ensure that the original error is preserved, and other error handling should be investigated to look for similar issues.
  2. Expected behaviour:
  3. Actual behaviour:
  4. Error message/stack trace:
  5. Any other details that can be helpful:

Screenshots

  • If applicable, add screenshots to help explain your problem.

JDBC log

  • Add related JDBC log entries here.
@birschick-bq birschick-bq added the bug Something isn't working label Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant