You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Adriano (JIRA)" <ji...@apache.org> on 2018/05/15 11:25:00 UTC
[jira] [Created] (IMPALA-7031) Detailed failure reason for clients
when a query is cancelled from the WebUi
Adriano created IMPALA-7031:
-------------------------------
Summary: Detailed failure reason for clients when a query is cancelled from the WebUi
Key: IMPALA-7031
URL: https://issues.apache.org/jira/browse/IMPALA-7031
Project: IMPALA
Issue Type: New Feature
Reporter: Adriano
In big clusters with many jdbc/odbc users, in order to save resources are often implemented scripts that automatically cancel queries (e.g. long running queries) (the scripts typically are using the Impala Webui).
Typical Scenario:
# A jdbc/odbc client submit a query
# The Coordinator start the query execution
# The query is cancelled from the Coordinator WebUi
# The jdbc/odbc client ask to the Coordinator the query status (GetOperationStatus)
# The Coordinator answer "unknown query ID" (as the query was cancelled)
# For the client perspective the query failed for "unknown query ID"
Currently, if a running query is cancelled from the impalad WebUI, the client will just receive an 'unknown query ID' error on the next fetch/getOperationStatus attempt. It would be good to be able to explicitly call out this case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)