[
https://issues.apache.org/jira/browse/HIVE-26564?focusedWorklogId=812343&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-812343
]
ASF GitHub Bot logged work on HIVE-26564:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 27/Sep/22 03:49
Start Date: 27/Sep/22 03:49
Worklog Time Spent: 10m
Work Description: yigress commented on PR #3621:
URL: https://github.com/apache/hive/pull/3621#issuecomment-1258933010
Thank you @dengzhhu653 so much for your review! The reason for this
change is that we want to add a feature to persist the hive QueryInfo and
OperationLog at first, for example, persist the information on HDFS or other
storage, for ephemeral clusters. Right now only a limited number of historical
queries are available in hs2 UI. So OperationLogManager seems an ideal place
to do that, or some other ways outside hive that look at the historical
operation log location, but current mixing live queries inside historical dir
makes it harder to differentiate.
Issue Time Tracking
-------------------
Worklog Id: (was: 812343)
Time Spent: 1h 10m (was: 1h)
> Separate query live operation log and historical operation log
> --------------------------------------------------------------
>
> Key: HIVE-26564
> URL: https://issues.apache.org/jira/browse/HIVE-26564
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 4.0.0-alpha-2
> Reporter: Yi Zhang
> Assignee: Yi Zhang
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> HIVE-24802 added OperationLogManager to support historical operation logs.
> OperationLogManager.createOperationLog creates operation log inside
> historical operation log dir if
> HIVE_SERVER2_HISTORIC_OPERATION_LOG_ENABLED=true. This is confusing, since on
> session level, SessionManager and HiveSession are using original operation
> log session directory.
> Proposed change is to separate live query's operation log and historical
> operation log. Upon operation close, OperationLogManager.closeOperation is
> called to move the operation log from session directory to historical log
> dir. OperationLogManager is only responsible to clean up historical operation
> logs.
> This change also makes it easier to manage historical logs, for example, user
> may want to persist historical logs, it is easier to differentiate live and
> historical operation logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
