hudi-bot opened a new issue, #15500: URL: https://github.com/apache/hudi/issues/15500
When clustering is disabled after being enabled, the inflight clustering replacecommit scheduled and executed before will stay in the active timeline indefinitely, blocking the metadata table compaction and data table archival. We should add a logic to roll back inflight clustering replacecommit when clustering is disabled. This should be guarded by a feature flag so if clustering has never been enabled, there is no need to exercise the logic which can introduce overhead of checking clustering intants. ## JIRA info - Link: https://issues.apache.org/jira/browse/HUDI-5044 - Type: Improvement -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
