[
https://issues.apache.org/jira/browse/IMPALA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alice Fan updated IMPALA-7031:
------------------------------
Summary: Add additional info to query canceled from http endpoint (was:
Debug page "Cancel" action actually unregisters query)
> Add additional info to query canceled from http endpoint
> --------------------------------------------------------
>
> Key: IMPALA-7031
> URL: https://issues.apache.org/jira/browse/IMPALA-7031
> Project: IMPALA
> Issue Type: New Feature
> Components: Distributed Exec
> Affects Versions: Impala 3.0
> Reporter: Adriano
> Assignee: Alice Fan
> Priority: Major
> Labels: query-lifecycle
> Attachments: Screen Shot 2018-07-20 at 10.19.42.png
>
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
