[
https://issues.apache.org/jira/browse/HIVE-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228794#comment-15228794
]
Mohit Sabharwal commented on HIVE-13420:
----------------------------------------
LGTM.
Some suggestions on naming, just so it's more clear to the user.
1) "End Time" -> "Operation Close Timestamp"
Also, since this is the time when op was closed, instead of saying "In
Progress" as the default value, we can just say "Open" (since we don't know if
the op is running)
2) "Query Runtime (s) " -> "Latency (s)"
3) "Opened (s)" -> "Operation Open For (s)"
We may want to put columns 1) and 3) next to each other since they are related
(both depend on client closing the session/operation).
The word Query in "Query Drilldown" seems redundant - we could just say
"Drilldown"
> Clarify HS2 WebUI Query 'Elapsed TIme'
> --------------------------------------
>
> Key: HIVE-13420
> URL: https://issues.apache.org/jira/browse/HIVE-13420
> Project: Hive
> Issue Type: Improvement
> Components: Diagnosability
> Affects Versions: 2.0.0
> Reporter: Szehon Ho
> Assignee: Szehon Ho
> Attachments: Elapsed Time.png, HIVE-13420.patch, Patched UI.png
>
>
> Today the "Queries" section of the WebUI shows SQLOperations that are not
> closed.
> Elapsed time is thus a bit confusing, people might take this to mean query
> runtime, actually it is the time since the operation was opened. The query
> may be finished, but operation is not closed. Perhaps another timer column
> is needed showing the runtime of the query to reduce this confusion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
