[
https://issues.apache.org/jira/browse/HIVE-23803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151910#comment-17151910
]
Denys Kuzmenko commented on HIVE-23803:
---------------------------------------
[~pvary], I think, issue is that for that table which has `NO_AUTO_COMPACTION`
set as true, we might end up with huge number of deltas and when user decides
to activate compaction for this table we won't be able to execute it unless
there is a new entry in completed transaction component table. [~aditya-shah],
is that correct?
> Initiator misses compactions of table which were just allowed auto compaction
> after a given interval
> ----------------------------------------------------------------------------------------------------
>
> Key: HIVE-23803
> URL: https://issues.apache.org/jira/browse/HIVE-23803
> Project: Hive
> Issue Type: Bug
> Reporter: Aditya Shah
> Priority: Major
>
> After HIVE-21917 we are just looking at completed transaction components
> entries that have a timestamp in past check interval for initiators. But if
> there is a table which has `NO_AUTO_COMPACTION` set as true for a while (at
> least check interval) and is toggled to false, auto compaction will not
> happen for that table till there is no new entry in completed transaction
> component.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
