[SPARK-51756][CORE][FOLLOWUP] Fix code style issues#52521
Closed
ivoson wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-51756][CORE][FOLLOWUP] Fix code style issues#52521ivoson wants to merge 1 commit intoapache:masterfrom
ivoson wants to merge 1 commit intoapache:masterfrom
Conversation
Contributor
Author
|
cc @cloud-fan |
Member
|
Let's avoid making a PR for such style changes. It's not really worth while spending time on this in a separate PR. we can fix it together when we happen to touch the code around here. |
Contributor
Author
Sure. Closing this then. |
Contributor
|
This is a quick followup to fix the wrong code style introduced by a recently merged PR from the same PR author, I think we should accept it? @HyukjinKwon |
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.
What changes were proposed in this pull request?
This is a follow up of #50230 to fix the code style issues in
MapStatusEndToEndSuite.Why are the changes needed?
Fix indentation issue.
Does this PR introduce any user-facing change?
No
How was this patch tested?
NA
Was this patch authored or co-authored using generative AI tooling?
No