You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/05/09 03:31:12 UTC

[jira] [Resolved] (CALCITE-1218) Mishandling of uncaught exceptions results in no ErrorResponse sent to client

     [ https://issues.apache.org/jira/browse/CALCITE-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved CALCITE-1218.
---------------------------------
    Resolution: Fixed

Fixed in https://git1-us-west.apache.org/repos/asf?p=calcite.git;a=commit;h=fa87c0621fde841d2b1a40b8fb0048ed70ea576a.

One annoying piece was that I couldn't get a test written for this how I wanted to. Ultimately, this stemmed from the relocation of protobuf classes in the avatica dependency. CALCITE-1224 will address this moving forward.

> Mishandling of uncaught exceptions results in no ErrorResponse sent to client
> -----------------------------------------------------------------------------
>
>                 Key: CALCITE-1218
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1218
>             Project: Calcite
>          Issue Type: Bug
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Blocker
>             Fix For: avatica-1.8.0
>
>
> In doing some testing of the Kerberos auth for Avatica, I noticed another area (in AvaticaProtobufHandler) which did not create and return an ErrorResponse to the user. This shows up in the client with an obtuse error message of "Cannot find parser for empty message class" (or similar).
> Before 1.8.0 comes out, we need to:
> # Squash this issue once and for all (catch all exceptions and create an ErrorResponse)
> # Improve the client error message



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)