zhangyue19921010 opened a new pull request, #12448: URL: https://github.com/apache/hudi/pull/12448
### Change Logs In Hudi, when scheduling Compaction, the default behavior is to scan all partitions under the current table. When there are many historical partitions, such as 640,000 in our production environment, this scanning and planning operation becomes very inefficient. For Flink, it often leads to checkpoint timeouts, resulting in data delays. This PR introduces the ability to schedule Compaction for incremental partitions. In the StreamOperatorCoordinator, it adds: 1. A state variable `lastInstant` to record the delta commit instant corresponding to the last successfully completed Compaction schedule, and it is saved with the state. 2. A temporary variable `cacheWrittenPartitions` to cache the incremental partitions corresponding to all delta commits from the last scheduled Compaction to the present. <img width="1494" alt="image" src="https://github.com/user-attachments/assets/2f7de73d-30ad-4411-ba08-28386ff549f4";> ### Impact _Describe any public API or user-facing feature change or any performance impact._ ### Risk level (write none, low medium or high below) _If medium or high, explain what verification was done to mitigate the risks._ ### Documentation Update _Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none"._ - _The config description must be updated if new configs are added or the default value of the configs are changed_ - _Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the ticket number here and follow the [instruction](https://hudi.apache.org/contribute/developer-setup#website) to make changes to the website._ ### Contributor's checklist - [ ] Read through [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [ ] Change Logs and Impact were stated clearly - [ ] Adequate tests were added if applicable - [ ] CI passed -- 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]
