Version

5.6.0-SNAPSHOT

Feature

Aborting an HTTP query execution waits until the input stream of the HTTP response becomes available - which can take a while if e.g. the connection request hangs or the time to the first result row is high. Arguably, the expected behavior of abort() is to return quickly even in these situations. The underlying reason is, that the synchronous API of the HTTP client is used, whereas the async one would allow one to cancel the java future of the ongoing request.

This issue was encountered while testing the execution tracker UI of #3184 , where clicking the abort button would hang.

Are you interested in contributing a solution yourself?

Yes