[
https://issues.apache.org/jira/browse/IMPALA-7031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476046#comment-16476046
]
Tim Armstrong commented on IMPALA-7031:
---------------------------------------
[~adrenas] I think this is only possible if the query is "closed" from the web
UI, not just cancelled. If you can reproduce with the query still in the
"waiting to be closed" state then something weird is going on.
> 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
> Priority: Major
>
> 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: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
