[
https://issues.apache.org/jira/browse/CALCITE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380403#comment-14380403
]
Julian Hyde commented on CALCITE-645:
-------------------------------------
I presume each client API (e.g. ODBC) has a way to propagate errors. The
information content probably differs but has at its core an error message,
error code, severity (e.g. error versus warning) and maybe a list of causing
errors and stack dump as string. I think a JSON-ified SQLException (including
its "next" and "cause" exceptions, SQLcode, sub-class, stack trace) will serve
these APIs too.
Might be worth a quick look at the ODBC spec to validate. Everything else is
likely built on ODBC or JDBC.
> Pass server-side exceptions back to the client
> ----------------------------------------------
>
> Key: CALCITE-645
> URL: https://issues.apache.org/jira/browse/CALCITE-645
> Project: Calcite
> Issue Type: Improvement
> Reporter: Nick Dimiduk
> Assignee: Julian Hyde
>
> Avatica RPC response objects should contain an exception field that can be
> deserialized and re-thrown on the client side. That way client sees stack
> traces that are more meaningful than "500 error".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
