You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Shant Hovsepian (Jira)" <ji...@apache.org> on 2020/10/13 02:51:00 UTC
[jira] [Commented] (IMPALA-9343) Ensure that multithreaded plans
are shown correctly in exec summary, profile, etc.
[ https://issues.apache.org/jira/browse/IMPALA-9343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212798#comment-17212798 ]
Shant Hovsepian commented on IMPALA-9343:
-----------------------------------------
Posted a partial fix on [https://gerrit.cloudera.org/c/16588/]
It treats JoinBuildSink fragments similarly to DataStreamSink fragments, so we get a dashed lined into the join node to signify the fragment acting as the source. I'm not sure if we want to call out the join build instead.
!mt_plan.png!
> Ensure that multithreaded plans are shown correctly in exec summary, profile, etc.
> ----------------------------------------------------------------------------------
>
> Key: IMPALA-9343
> URL: https://issues.apache.org/jira/browse/IMPALA-9343
> Project: IMPALA
> Issue Type: Task
> Reporter: Tim Armstrong
> Assignee: Joe McDonnell
> Priority: Major
> Labels: multithreading, observability
> Attachments: mt_dop_plan.json, mt_dop_webui_plan.png, mt_plan.png, non_mt_dop_plan.json, non_mt_dop_webui_plan.png
>
>
--
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