[fix][PES][datasource] fix datasource oom issue in mdq service partition statistic#1040
Merged
Merged
Conversation
aiceflower
pushed a commit
that referenced
this pull request
Jun 15, 2026
aiceflower
pushed a commit
that referenced
this pull request
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Background/Problem:
The partition statistic method in MdqServiceImpl uses forEach with Lambda expressions, which can cause OOM (Out of Memory) issues when processing large partitions. The functional programming style creates multiple intermediate objects that increase memory pressure.
Purpose of Change:
To address this OOM problem, this PR refactors the
getMdqTablePartitionStatisticInfoVOmethod by replacing forEach + Lambda expressions with traditional for-each loops, reducing object creation and improving memory efficiency.Value/Impact:
After the change, the system can handle large partition lists without OOM errors, improving stability and reliability in production environments.
Related issues/PRs
Related issues: close #1039
Related pr:none
Brief change log
Checklist