[MINOR][SQL][FOLLOWUP] Fix scalastyle in LimitPushDownThroughWindow #40386
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
|
cc @wangyum and @kenny-ddd |
|
Scala linter passed.
|
|
Hi, @bjornjorgensen . Could you review this PR? |
|
Could you review this in order to recover master branch, @sunchao ? |
|
Since this is a comment only change, let me merge this to recover the master branch and PRs.
|
|
Merged to master. |
|
@dongjoon-hyun Thank you. Yes, this PR looks ok. |
|
Thank you so much, @bjornjorgensen . |
|
I have seen this one time before. Can you restart tests on the PR that fails? |
|
No, only the PR author can do that because we use the author's GitHub Actions for that PR.
For Apache Spark branch, of course, you can because you are the committer. |
|
Seams to be working now :) |
|
Thanks for your fix @dongjoon-hyun |
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?
Although this is weird because of `[MINOR][SQL][FOLLOWUP]'. This PR aims to recover the CI failure on the master branch from the following commit.
c75b3ab
Why are the changes needed?
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.