You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Karen Coppage (JIRA)" <ji...@apache.org> on 2017/08/11 14:26:00 UTC
[jira] [Commented] (HIVE-17300) WebUI query plan graphs
[ https://issues.apache.org/jira/browse/HIVE-17300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123413#comment-16123413 ]
Karen Coppage commented on HIVE-17300:
--------------------------------------
[~xuefuz] Thanks very much for the suggestion to create a JIRA on this topic.
> WebUI query plan graphs
> -----------------------
>
> Key: HIVE-17300
> URL: https://issues.apache.org/jira/browse/HIVE-17300
> Project: Hive
> Issue Type: Improvement
> Components: Web UI
> Reporter: Karen Coppage
> Attachments: complete_success.png, full_mapred_stats.png, graph_with_mapred_stats.png, last_stage_error.png, last_stage_running.png, non_mapred_task_selected.png
>
>
> Hi all,
> I’m working on a feature of the Hive WebUI Query Plan tab that would provide the option to display the query plan as a nice graph (scroll down for screenshots). If you click on one of the graph’s stages, the plan for that stage appears as text below.
> Stages are color-coded if they have a status (Success, Error, Running), and the rest are grayed out. Coloring is based on status already available in the WebUI, under the Stages tab.
> There is an additional option to display stats for MapReduce tasks. This includes the job’s ID, tracking URL (where the logs are found), and mapper and reducer numbers/progress, among other info.
> The library I’m using for the graph is called vis.js (http://visjs.org/). It has an Apache license, and the only necessary file to be included from this library is about 700 KB.
> I tried to keep server-side changes minimal, and graph generation is taken care of by the client. Plans with more than a given number of stages (default: 25) won't be displayed in order to preserve resources.
> I’d love to hear any and all input from the community about this feature: do you think it’s useful, and is there anything important I’m missing?
> Thanks,
> Karen Coppage
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)