## What is the purpose of the change If exception currently happens on the server side in REST API handlers, the client side gets error response. The error response contains only an abstract message of the server side exception in the error list and no details. This PR adds also a stringified version of the stack trace of the server side exception. This way the stack trace in logs on the client side will also contain the stack trace of the server side with more details about actual failure.
## Brief change log - pack the stringified version of the exception stack trace into the error list of ErrorResponseBody in AbstractRestHandler.processRestHandlerException - strip CompletionException in completeExceptionally case of FutureUtils.retryOperationWithDelay to avoid double logging of underlying exception ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable) [ Full content available at: https://github.com/apache/flink/pull/6731 ] This message was relayed via gitbox.apache.org for [email protected]
