[SPARK-28901][SQL][FLLOW-UP] SparkThriftServer's Cancel SQL Operation show it in JDBC Tab UI #25691
Closed
AngersZhuuuu wants to merge 1 commit into
Closed
[SPARK-28901][SQL][FLLOW-UP] SparkThriftServer's Cancel SQL Operation show it in JDBC Tab UI #25691AngersZhuuuu wants to merge 1 commit into
AngersZhuuuu wants to merge 1 commit into
Conversation
Contributor
Author
|
@juliuszsompolski A little mistake, miss end status of FINISHED |
|
Can one of the admins verify this patch? |
Contributor
|
@AngersZhuuuu It's good now. FINISHED should not be there. A statement in FINISHED state can still be fetching results. |
Contributor
Author
Right， close it |
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
4 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?
For last pr #25611, seems I forgot one case when
getTotalRunning SQL numbers, I miss end status of FINISHED
Why are the changes needed?
Fix bug
Does this PR introduce any user-facing change?
No
How was this patch tested?
Existed UT