Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-49814][CONNECT] When Spark Connect Client starts, show the spark version of the connect server #48283

Closed
wants to merge 1 commit into from

Conversation

panbingkun
Copy link
Contributor

What changes were proposed in this pull request?

The pr aims to show the spark version of the connect server when Spark Connect Client starts.

Why are the changes needed?

With the gradual popularize of Spark Connect module, when the Spark Connect client starts, explicitly displaying the spark version of the connect server, will reduce confusion for users during execution, such as the new version having some features. However, if it connects to an old version and encounters some problems, it will have to manually troubleshoot.
image

Does this PR introduce any user-facing change?

Yes, Connect‘s end-users can intuitively know the Spark version on the server side when starting the client, reducing confusion.

How was this patch tested?

Manually check.

Was this patch authored or co-authored using generative AI tooling?

No.

@panbingkun
Copy link
Contributor Author

cc @HyukjinKwon

@HyukjinKwon
Copy link
Member

Merged to master.

attilapiros pushed a commit to attilapiros/spark that referenced this pull request Oct 4, 2024
…ark version` of the `connect server`

### What changes were proposed in this pull request?
The pr aims to show the spark version of the connect server when Spark Connect Client starts.

### Why are the changes needed?
With the gradual popularize of Spark Connect module, when the Spark Connect client starts, explicitly displaying the spark version of the `connect server`, will reduce confusion for users during execution, such as the new version having some features. However, if it connects to an old version and encounters some problems, it will have to manually troubleshoot.
<img width="878" alt="image" src="https://github.com/user-attachments/assets/c93026e8-03e7-4292-bae2-c3a0f4422191">

### Does this PR introduce _any_ user-facing change?
Yes, Connect‘s end-users can intuitively know the `Spark version` on the `server side` when starting the client, reducing confusion.

### How was this patch tested?
Manually check.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes apache#48283 from panbingkun/SPARK-49814.

Authored-by: panbingkun <panbingkun@baidu.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
himadripal pushed a commit to himadripal/spark that referenced this pull request Oct 19, 2024
…ark version` of the `connect server`

### What changes were proposed in this pull request?
The pr aims to show the spark version of the connect server when Spark Connect Client starts.

### Why are the changes needed?
With the gradual popularize of Spark Connect module, when the Spark Connect client starts, explicitly displaying the spark version of the `connect server`, will reduce confusion for users during execution, such as the new version having some features. However, if it connects to an old version and encounters some problems, it will have to manually troubleshoot.
<img width="878" alt="image" src="https://github.com/user-attachments/assets/c93026e8-03e7-4292-bae2-c3a0f4422191">

### Does this PR introduce _any_ user-facing change?
Yes, Connect‘s end-users can intuitively know the `Spark version` on the `server side` when starting the client, reducing confusion.

### How was this patch tested?
Manually check.

### Was this patch authored or co-authored using generative AI tooling?
No.

Closes apache#48283 from panbingkun/SPARK-49814.

Authored-by: panbingkun <panbingkun@baidu.com>
Signed-off-by: Hyukjin Kwon <gurwls223@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants