[
https://issues.apache.org/jira/browse/CALCITE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947703#comment-14947703
]
Julian Hyde commented on CALCITE-645:
-------------------------------------
I found [ODBC Diagnostics & Error Status
Codes|http://www.easysoft.com/developer/interfaces/odbc/diagnostics_error_status_codes.html],
which gives you an idea how to get multiple error or warning records back from
an ODBC statement, with a sqlstate, error code, and message. The data model is
basically the same as JDBC returning a list of SQLException objects, so the
data passing over the Avatica protocol should look similar.
> 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
> Components: avatica
> Reporter: Nick Dimiduk
> Assignee: Josh Elser
>
> 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)
