[SPARK-42025][SHUFFLE] Improve logs level in removeBlocks #54043
+2
−2
Conversation
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
JIRA Issue Information=== Improvement SPARK-42025 === This comment was automatically generated by GitHub Actions |
varun-lakhyani
force-pushed
the
change_logs_level
branch
from
f5800fa to
4d9ac53
Compare
Author
|
PTAL @mridulm @wankunde @otterc
1 is completed for RemoveBlocks but RemoveShuffleMerge doesnt use RPC send so can't infer onSuccess and onFailure in it. Should this client.send be replaced with client.sendRpc for RemoveShuffleMerge and implement similar to RemoveBlocks? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Changed log level from warn to info as discussed #37922 (comment)
Why are the changes needed?
Reduce logs pollution and improve readability
Does this PR introduce any user-facing change?
No
How was this patch tested?
No tests required, Just Logs level changed
Was this patch authored or co-authored using generative AI tooling?
No