[#1132] improvement(spark): Unregister shuffle explicitly when Spark application is stopped. #1139
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
jerqi
changed the title
Codecov Report
@@ Coverage Diff @@
## master #1139 +/- ##
============================================
+ Coverage 53.70% 54.81% +1.10%
- Complexity 2573 2574 +1
============================================
Files 391 371 -20
Lines 22314 19959 -2355
Branches 1867 1868 +1
============================================
- Hits 11984 10940 -1044
+ Misses 9622 8382 -1240
+ Partials 708 637 -71
... and 24 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
zuston
approved these changes
Aug 15, 2023
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?
Unregister shuffle explicitly when Spark application is stopped.
Why are the changes needed?
Fix: #1132
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Add more test cases.