[CELEBORN-1877] Bump zstd-jni version from 1.5.2-1 to 1.5.7-1 #3114
+10
−10
Conversation
This file contains 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
|
Ping @pan3793. |
|
I suppose the upgrade should have perf improvements for the Celeborn client because the default value of and zstd v1.5.7 release notes say
Note: Celeborn Spark shaded client does not ship the zstd-jni and always uses Spark's built-in zstd-jni, if someone wants to test the perf improvement, he/she should upgrade the Spark's built-in zstd-jni first. |
pan3793
approved these changes
Feb 24, 2025
RexXiong
approved these changes
Feb 25, 2025
turboFei
approved these changes
Feb 25, 2025
FMX
approved these changes
Feb 25, 2025
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 changes were proposed in this pull request?
Bump zstd-jni version from 1.5.2-1 to 1.5.7-1.
Why are the changes needed?
Bump zstd-jni to the latest version.
Backport apache/spark#50057.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No.