[
https://issues.apache.org/jira/browse/HIVE-12952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15128315#comment-15128315
]
Aihua Xu commented on HIVE-12952:
---------------------------------
+1. The patch looks good.
Possible future improvement to consider:
1. In Perf-log tab, if we can add a total time for compile and execution, that
could be helpful for us to see if compile or execution has the bottleneck.
2. The entries for compile stage should be divided into logical subtasks, like
how much time is spent on Parser, Logical Optimizer, Physical Optimizer, etc.
And each of them can be divided further.
{noformat}
Compile-time
Semantic Analysis 50
Parser 20
Optimizer 50
------------------------------------
Total 5600
{noformat}
> 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, HIVE-12952.2.patch,
> HIVE-12952.3.patch, HIVE-12952.4.patch, HIVE-12952.patch, Query Drilldown
> link.png, Tab 3 - Stages.png, Tab1- Base Profile.png, Tab2 - Query Plan.png,
> Tab4 - Perf Logging.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)
