impala-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Tauber-Marshall (Code Review)" <>
Subject [Impala-ASF-CR] IMPALA-5340: Query profile displays stale query state
Date Fri, 19 May 2017 20:59:38 GMT
Thomas Tauber-Marshall has posted comments on this change.

Change subject: IMPALA-5340: Query profile displays stale query state

Patch Set 2:

(1 comment)

> Any good way to regression test this?

Obviously its a timing issue when we'll advance query states, and without a good way to control
the timing tests run the risk of either being flaky or being too permissive to catch bugs.

One observation is with this change it will always be the case that after a call to ExecuteStatement
(for hs2, or the equivalent for beeswax), the query will have advanced past CREATED to RUNNING
or FINISHED (which was not the case before this patch) and after all rows have been fetched
the state will be FINISHED.

We could check for those things in tests, though I don't think they're required by the hs2
(or beeswax) spec so it may change in the future.
File be/src/service/client-request-state.h:

PS2, Line 413: must ensure lock_
> Any chance we can DCHECK it ?
>From looking through the boost documentation, I don't think so.

To view, visit
To unsubscribe, visit

Gerrit-MessageType: comment
Gerrit-Change-Id: I952319b7308a24d4e2dff924199c0c771bce25b3
Gerrit-PatchSet: 2
Gerrit-Project: Impala-ASF
Gerrit-Branch: master
Gerrit-Owner: Thomas Tauber-Marshall <>
Gerrit-Reviewer: Dan Hecht <>
Gerrit-Reviewer: Matthew Jacobs <>
Gerrit-Reviewer: Michael Ho <>
Gerrit-Reviewer: Thomas Tauber-Marshall <>
Gerrit-HasComments: Yes

View raw message