[DO-NOT-REVIEW] [SPARK-48093][SS][CONNECT][3.5] Add config to switch between client side and server side StreamingQueryListener#46341
Closed
WweiL wants to merge 1 commit intoapache:branch-3.5from
Closed
Conversation
Member
|
Since this is not for review, I'd recommend to open this PR to your repository. Your GitHub Action can verify your PR, @WweiL . |
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
2 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?
We are backporting the client side StreamingQueryListenr to branch-3.5. In case there is usage of server side listener and users want to preserve this behavior, add this config handler in server, also the client can retrieve the config from the server on what type of listener to use. Note that on 4.0 and upwards we only have client side listener implemented in python client. So this config should only be sent to clients with spark version 3.5.
Why are the changes needed?
Backward compatibility
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unit test
Was this patch authored or co-authored using generative AI tooling?
No