You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/04/01 09:19:00 UTC

[jira] [Commented] (FLINK-16217) SQL Client crashed when any uncatched exception is thrown

    [ https://issues.apache.org/jira/browse/FLINK-16217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17072563#comment-17072563 ] 

Aljoscha Krettek commented on FLINK-16217:
------------------------------------------

[~godfreyhe] Will you still work on this?

> SQL Client crashed when any uncatched exception is thrown
> ---------------------------------------------------------
>
>                 Key: FLINK-16217
>                 URL: https://issues.apache.org/jira/browse/FLINK-16217
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Client
>    Affects Versions: 1.10.0
>            Reporter: Jark Wu
>            Assignee: godfrey he
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 1.10.1, 1.11.0
>
>         Attachments: 15821324825831.jpg
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, SQL CLI doesn't catch all the exceptions, for example, Calcite exceptions. 
> We should catch any possible exceptions thrown by the planner, and print the root cause. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)