Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-6332

Impala webserver should return HTTP error code for missing query profiles

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: Impala 2.10.0, Impala 2.11.0
    • Fix Version/s: None
    • Component/s: Backend
    • Labels:
      None
    • Epic Color:
      ghx-label-8

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              zoram Zoram Thanga
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: