You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Marta Kuczora (Jira)" <ji...@apache.org> on 2026/09/29 09:02:00 UTC

[jira] [Resolved] (HIVE-29532) FindPotentialCompactions method is Truncating out some records, even though corresponding entries still exist in COMPLETED_TXN_COMPONENTS

     [ https://issues.apache.org/jira/browse/HIVE-29532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marta Kuczora resolved HIVE-29532.
----------------------------------
    Fix Version/s: NA
       Resolution: Duplicate

This is the same issue as in [HIVE-30026|https://issues.apache.org/jira/browse/HIVE-30026], so closing this as duplicate.

> FindPotentialCompactions method is Truncating out some records, even though corresponding entries still exist in COMPLETED_TXN_COMPONENTS
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-29532
>                 URL: https://issues.apache.org/jira/browse/HIVE-29532
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 4.0.0, 4.1.0, 4.0.1, 4.2.0
>            Reporter: Denys Kuzmenko
>            Priority: Major
>             Fix For: NA
>
>
> *Problem Statement* -  Hive Compaction Initiator not initiating compaction for few tables. 
> Every Initiator cycle hits exactly 1000 candidates (COMPACTOR_FETCH_SIZE limit) and ignores the rest on the next cycle
> In findPotentialCompactions, the condition TC.CTC_TIMESTAMP >= CURRENT_TIMESTAMP - INTERVAL 300 SECOND, returns rows where CTC_TIMESTAMP is within the last 300 seconds, i.e., the last 5 minutes.
> The next cycle doesn't pick this table due to the above condition hence it remains in the table itself. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)