[
https://issues.apache.org/jira/browse/CALCITE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378992#comment-14378992
]
Julian Hyde commented on CALCITE-645:
-------------------------------------
Agreed. Ultimately the JDBC client driver should throw a SQLException or
sub-class. The JDBC client has a bad habit of throwing RuntimeExceptions right
now.
When re-constructing the chain of exceptions, I don't recommend that you try to
create exceptions of the same type. The type may not exist on the client. As
long as the call stack string comes through, we should be OK.
> 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)
