[
https://issues.apache.org/jira/browse/HIVE-26908?focusedWorklogId=837818&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-837818
]
ASF GitHub Bot logged work on HIVE-26908:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/23 08:14
Start Date: 09/Jan/23 08:14
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on PR #3915:
URL: https://github.com/apache/hive/pull/3915#issuecomment-1375246625
@tarak271 it looks Ok, however, we have an alternative option to do the
same, disable auto-compaction on DB level, see
https://github.com/apache/hive/pull/3822 cc @veghlaci05
Issue Time Tracking
-------------------
Worklog Id: (was: 837818)
Time Spent: 1h (was: 50m)
> Disable Initiator on HMS instance at the same time enable Cleaner thread
> ------------------------------------------------------------------------
>
> Key: HIVE-26908
> URL: https://issues.apache.org/jira/browse/HIVE-26908
> Project: Hive
> Issue Type: New Feature
> Components: Standalone Metastore
> Reporter: Taraka Rama Rao Lethavadla
> Assignee: Taraka Rama Rao Lethavadla
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In the current implementation, both Initiator and Cleaner are either enabled
> or disabled using the same config
> {noformat}
> hive.compactor.initiator.on{noformat}
> So there is no way to selectively disable initiator and enable cleaner or
> vice versa.
> Introducing another config to handle Cleaner thread alone like
> hive.compactor.cleaner.on
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
