[
https://issues.apache.org/jira/browse/HIVE-24802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17289235#comment-17289235
]
David Mollitor commented on HIVE-24802:
---------------------------------------
Not sure I love this feature.
I worry about controlling the amount of data that gets stored here on the local
host. On a busy system, this could be hundreds (thousands?) of operations
stored. There would need to be a cap. Also, what if HS2 crashes? Will HS2
load the directory and look at the existing operations or does it only act on
new ones that come in? I worry about exposing too much data to one admin user.
How are access controls enforced on viewing these logs through the UI?
I would rather implement something like [HIVE-24574].
> Show operation log at webui
> ---------------------------
>
> Key: HIVE-24802
> URL: https://issues.apache.org/jira/browse/HIVE-24802
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently we provide getQueryLog in HiveStatement to fetch the operation log,
> and the operation log would be deleted on operation closing(delay for the
> canceled operation). Sometimes it's would be not easy for the user(jdbc) or
> administrators to deep into the details of the finished(failed) operation, so
> we present the operation log on webui and keep the operation log for some
> time for latter analysis.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
