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

Posted to issues@flink.apache.org by "Shengkai Fang (Jira)" <ji...@apache.org> on 2022/12/14 11:53:00 UTC

[jira] [Closed] (FLINK-29946) Introduce ‘ErrorDetail’ in SQL Gateway Rest Endpoint for error handling

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

Shengkai Fang closed FLINK-29946.
---------------------------------
    Resolution: Invalid

> Introduce ‘ErrorDetail’ in SQL Gateway Rest Endpoint for error handling
> -----------------------------------------------------------------------
>
>                 Key: FLINK-29946
>                 URL: https://issues.apache.org/jira/browse/FLINK-29946
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / Client, Table SQL / Gateway
>    Affects Versions: 1.17.0
>            Reporter: yuzelin
>            Priority: Major
>
> In embedded mode of SQL Client, the exception can be caught by the client finally, but in remote mode, all message return should be serialized and deserialized by REST API. Currently, the Gateway endpoint only returns the exception stack as List<String> when exceptions are thrown. It’s hard for Client to get more useful information. So it's necessary to introduce an 'ErrorDetail' to provide more information.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)