You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2022/01/12 03:38:00 UTC

[jira] [Commented] (HUDI-2511) Aggressive archival configs compared to cleaner configs make cleaning moot

    [ https://issues.apache.org/jira/browse/HUDI-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17473275#comment-17473275 ] 

sivabalan narayanan commented on HUDI-2511:
-------------------------------------------

Closing this out since we have a patch addressing the issue.

> Aggressive archival configs compared to cleaner configs make cleaning moot
> --------------------------------------------------------------------------
>
>                 Key: HUDI-2511
>                 URL: https://issues.apache.org/jira/browse/HUDI-2511
>             Project: Apache Hudi
>          Issue Type: Improvement
>            Reporter: sivabalan narayanan
>            Assignee: sivabalan narayanan
>            Priority: Blocker
>              Labels: core-flow-ds, sev:high, user-support-issues
>
> if hoodie.keep.max.commits <= hoodie.cleaner.commits.retained, then cleaner will never kick in only. Bcoz, by then archival will kick in and will move entries from active to archived. 
> We need to revisit this and either throw exception or make cleaner also look into archived commits. 
> Related issue: [https://github.com/apache/hudi/issues/3739]
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)