You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Zoram Thanga (JIRA)" <ji...@apache.org> on 2017/12/15 23:02:00 UTC
[jira] [Created] (IMPALA-6332) Impala webserver should return HTTP
error code for missing query profiles
Zoram Thanga created IMPALA-6332:
------------------------------------
Summary: Impala webserver should return HTTP error code for missing query profiles
Key: IMPALA-6332
URL: https://issues.apache.org/jira/browse/IMPALA-6332
Project: IMPALA
Issue Type: Bug
Components: Backend
Affects Versions: Impala 2.10.0, Impala 2.11.0
Reporter: Zoram Thanga
Priority: Minor
Fix For: Impala 2.11.0
When we try to read the thrift runtime profile of a query soon after the query is finished, sometimes the profile cannot be found in either the query map or query log. Then the server sends back "Query id $0 not found." from ImpalaServer::GetRuntimeProfileStr(). This is followed up in ImpalaHttpHandler::QueryProfileEncodedHandler() as:
ss.str(Substitute("Could not obtain runtime profile: $0", status.GetDetail()));
The string us returned to the caller, but the HTTP response code is OK. This can fool clients into thinking that they successfully read a valid thrift profile. But since that's not true, clients that deserialize the thrift profile may think that they received a corrupted profile.
We should change the code to send back a non-OK response, such as 404 in this situation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)