[AMORO-6789]Memory leaks when using mix -hive format to write parquet files.#2820
Merged
zhoujinsong merged 1 commit intoapache:masterfrom May 9, 2024
Merged
[AMORO-6789]Memory leaks when using mix -hive format to write parquet files.#2820zhoujinsong merged 1 commit intoapache:masterfrom
zhoujinsong merged 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
@zhoujinsong TBR |
zhoujinsong
approved these changes
May 9, 2024
Contributor
zhoujinsong
left a comment
zhoujinsong
left a comment
There was a problem hiding this comment.
LGTM.
Thanks for the contribution!
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
3 participants
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.
Fix bug that memory leaks when using mix -hive format to write parquet files.
Why are the changes needed?
To avoid writing tasks causing memory leak when write a mix-formatted table. Details refers to issue pls.
Close #2789 .
Brief change log
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation