Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Invalid
-
1.17.0
-
None
-
None
Description
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.
Attachments
Issue Links
- relates to
-
FLINK-29948 Add rootCause for ErrorResponse
- Open