[
https://issues.apache.org/jira/browse/HIVE-26908?focusedWorklogId=837875&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-837875
]
ASF GitHub Bot logged work on HIVE-26908:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 09/Jan/23 10:24
Start Date: 09/Jan/23 10:24
Worklog Time Spent: 10m
Work Description: tarak271 commented on PR #3915:
URL: https://github.com/apache/hive/pull/3915#issuecomment-1375395996
@deniskuzZ, @veghlaci05 The use case is that user wants to stop auto
compaction for all Databases/Tables forever. Run compaction manually on tables
as needed, so worker's task is done. But he wants cleaner to be running so as
to remove obsolete directories post manual compaction. Disabling DB level
compaction is good when user wants to enable auto compaction only for specific
databases and not all.
Issue Time Tracking
-------------------
Worklog Id: (was: 837875)
Time Spent: 1h 10m (was: 1h)
> 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 10m
> 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)
