You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "nsivabalan (via GitHub)" <gi...@apache.org> on 2026/06/25 02:23:22 UTC
Re: [I] Aggressive archival configs compared to cleaner configs make cleaning moot [hudi]
nsivabalan commented on issue #14875:
URL: https://github.com/apache/hudi/issues/14875#issuecomment-4795275030
Triage note: this looks resolved on current `master`. The archival service auto-adjusts `min/maxInstantsToKeep` at runtime so it never archives instants the cleaner is still retaining — see `ArchivalUtils.getMinAndMaxInstantsToKeep` (hudi-client/hudi-client-common/.../ArchivalUtils.java), which derives the floor from the cleaner's `earliestCommitToRetain` for all three policies (`KEEP_LATEST_COMMITS`, `KEEP_LATEST_BY_HOURS`, `KEEP_LATEST_FILE_VERSIONS`). The validation in `HoodieWriteConfig.Builder.validate()` intentionally only warns now ("The Hudi archiver will automatically adjust the configuration regardless"), which also covers @pushpavanthar's earlier comment about `KEEP_LATEST_BY_HOURS` being missed by the static check. Closing seems reasonable unless someone can reproduce on a recent release.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@hudi.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org