[jira] [Commented] (IMPALA-5783) Investigate exec summary behavior

["Tim Armstrong (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099428#comment-17099428 ] 

Tim Armstrong commented on IMPALA-5783:
---------------------------------------

[~twmarshall] I think we might have fixed this between IMPALA-6742 and IMPALA-341. IMPALA-341 fixed that query lifecycle bug with status reports. IMPALA-6742 should mean that profiles fetched before query unregistration have the summary added in. Am I missing something? 

> Investigate exec summary behavior
> ---------------------------------
>
>                 Key: IMPALA-5783
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5783
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.10.0
>            Reporter: Thomas Tauber-Marshall
>            Priority: Major
>              Labels: profile, query-lifecycle
>
> A recent investigation into a flaky test, IMPALA-5708, brought up the issue that the exec summary may not always be filled in for certain queries, even if the query is FINISHED.
> For example, a query with a limit or subquery that internally cancels some fragments because they are no longer needed may never update the exec summary with info from those fragments.
> We should investigate what guarantees we can make about when the exec summary will be present and add automated tests to check these guarantees.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org