[ 
https://issues.apache.org/jira/browse/HIVE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Szehon Ho updated HIVE-12952:
-----------------------------
    Attachment: Tab2 - Query Plan.png
                Tab1- Base Profile.png
                Tab 4 - Perf Logging.png
                Tab 3 - Stages.png
                Query Drilldown link.png
                Error - Query Info Expired.png

Attaching some screenshots:

With this patch, queries (current and historic) shown on HS2 WebUI now link a 
query sub-page, with detailed information of query on different tabs:

1.  Tabl- Base Info, ie user, query string, query id, begin time, end time, 
execution engine, error (if any)
2.  Tab2- Query Plan
3.  Tab3- Stages (MR jobs), their progress and info
4.  Tab4- Call trace info captured from HMSClient and PerfLogger.

Other screenshots also show the actual link from main-page, and also error 
message if query has been expired due to 
"hive.server2.webui.max.historic.queries" being exceeded.

> Show query sub-pages on webui
> -----------------------------
>
>                 Key: HIVE-12952
>                 URL: https://issues.apache.org/jira/browse/HIVE-12952
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Diagnosability
>            Reporter: Szehon Ho
>            Assignee: Szehon Ho
>         Attachments: Error - Query Info Expired.png, Query Drilldown 
> link.png, Tab 3 - Stages.png, Tab 4 - Perf Logging.png, Tab1- Base 
> Profile.png, Tab2 - Query Plan.png
>
>
> Today the queries showing in Running and Completed lists have some basic 
> information like query string, elapsed time, state, user, etc.
> It may be helpful to have even more information like:
> * Job URL's, job status
> * Explain plan (configurable)
> * Error message (if failure)
> * Dynamic metrics, incl:
>  ** Number of Tables/partitions fetched
>  ** Time taken in each method via perf-logger.
> These should go in another page, so as not to clog the summary hiveserver.jsp 
> page.
> This JIRA aims to tackle some of those.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to