Zouxxyy opened a new issue, #9019: URL: https://github.com/apache/hudi/issues/9019
**_Tips before filing an issue_** At present, hudi's compaction plan generation strategy is that if a FG appears in a certain plan, the FG will not enter the plan again; For asynchronous compaction scenarios, if a plan is not executed in time, then if there is other data written to the FG later, the log file will continue to grow, which will cause the next plan to have a lot of log files, increasing the risk of compaction OOM; Can we support that if a FG appears in a certain plan, the FG can still be generated in the plan? -- 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]
