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

Posted to commits@hudi.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/07/19 17:12:00 UTC

[jira] [Updated] (HUDI-4424) add new compactoin trigger stratgy: NUM_COMMITS_AFTER_REQUEST

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

ASF GitHub Bot updated HUDI-4424:
---------------------------------
    Labels: pull-request-available  (was: )

> add new compactoin trigger stratgy: NUM_COMMITS_AFTER_REQUEST
> -------------------------------------------------------------
>
>                 Key: HUDI-4424
>                 URL: https://issues.apache.org/jira/browse/HUDI-4424
>             Project: Apache Hudi
>          Issue Type: Improvement
>            Reporter: Jian Feng
>            Priority: Major
>              Labels: pull-request-available
>
> For now, NUM_COMMITS or TIME_ELAPSED compaction trigger strategy will check the number or time of delta-commits after the last successful compaction. so if the offline compaction application crash for a while, there will be a lot of compaction request（one request per delta commit） in the timeline.
> one customer complained about this, so I provide a new strategy not to check the last successful compaction but check the last compaction request.



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