You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Thomas Tauber-Marshall (Jira)" <ji...@apache.org> on 2020/05/13 19:04:00 UTC
[jira] [Resolved] (IMPALA-5783) Investigate exec summary behavior
[ https://issues.apache.org/jira/browse/IMPALA-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Tauber-Marshall resolved IMPALA-5783.
--------------------------------------------
Resolution: Fixed
Yeah, agreed that the issues here have been addressed now
> 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)