[
https://issues.apache.org/jira/browse/HIVE-12484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220392#comment-15220392
]
Mohit Sabharwal commented on HIVE-12484:
----------------------------------------
Thanks. You're right, query drilldown is not needed for meta or set operations
. That link currently leads to a page with all empty fields. I'll get rid of
the link for these ops.
One big advantage of putting all operations in the one live/historical section
is that user can get a chronologically ordered history of operations.
Especially useful for non-beeline jdbc client users, where the user via the
client may issue bunch of metadata requests (gettables, etc), then set some
configs and then issue user queries. Separate sections like live Sql ops,
historical Sql ops, live meta ops, historical meta ops, etc... also might make
the page more cluttered.
> Show meta operations on HS2 web UI
> ----------------------------------
>
> Key: HIVE-12484
> URL: https://issues.apache.org/jira/browse/HIVE-12484
> Project: Hive
> Issue Type: Sub-task
> Components: HiveServer2
> Reporter: Jimmy Xiang
> Assignee: Mohit Sabharwal
> Attachments: HIVE-12484.patch, MetaAndSetOps.png
>
>
> As Mohit pointed out in the review of HIVE-12338, it is nice to show meta
> operations on HS2 web UI too. So that we can have an end-to-end picture for
> those operations access HMS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
