TheR1sing3un opened a new issue, #17761: URL: https://github.com/apache/hudi/issues/17761
### Task Description **What needs to be done:** Reduce unnecessary timeline loading on the Flink-TM side **Why this task is needed:** Currently, in the Flink-TM logic when write to hudi table, there are some logics for creating `HoodieFlinkTable` objects. such as: <img width="1304" height="308" alt="Image" src="https://github.com/user-attachments/assets/45b2c831-8859-4007-9078-0feca7c022ad"; /> However, the current implementation will immediately load the active timeline after creating this object. <img width="897" height="235" alt="Image" src="https://github.com/user-attachments/assets/9c99cde0-3788-4d67-a133-8d7939403c48"; /> When there are a particularly large number of transactions on the active timeline, for instance, in our scenario, there might be tens of thousands of instants in active timeline. At this point, loading the timeline will become extremely **heavy**. Moreover, many subsequent logics do not rely on the relevant information of the active timeline. That is to say, immediately loading the timeline in these logics is an **unnecessary** operation. As the checkpoint interval of our real-time tasks becomes shorter, this performance impact becomes more obvious. So I think it is possible to optimize and reduce these unnecessary timeline loads ### Task Type Performance optimization ### Related Issues **Parent feature issue:** (if applicable ) **Related issues:** NOTE: Use `Relationships` button to add parent/blocking issues after issue is created. -- 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]
