[
https://issues.apache.org/jira/browse/SPARK-59136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated SPARK-59136:
---------------------------------
Description:
Alongside the Rust Spark Connect client, pyspark-client-rust installs the same
pyspark API surface backed by the native Rust engine (tonic). Because it
installs under the `pyspark` import name as a drop-in for the reference
pyspark-client, it should be easy to tell - at runtime, on PyPI, and in the
docs - which client is in use, so behavior and bug reports are attributed to
the right project.
This adds:
- Runtime identity markers: pyspark.__rust_client__ (True) and
pyspark.__engine__ ("rust").
- A one-time INFO log on first session connect identifying the Rust-backed
client.
- A "Which client am I using?" docs page (pyspark vs pyspark-client vs
pyspark-client-rust, how to tell them apart, where to file issues, server
compatibility), linked from the docs home and the Compatibility page.
- Install/uninstall guidance: because all three packages share the `pyspark`
import directory, the Installation docs spell out that you must uninstall the
existing client before installing (not on top of it), and that uninstalling
pyspark-client-rust alone leaves no working pyspark - you must reinstall
pyspark-client/pyspark to switch back.
- Sharpened PyPI metadata (description, keywords, Documentation URL).
Follow-up from the dev@ discussion on the Python wrapper of the Rust Connect
client.
was:
Alongside the Rust Spark Connect client, pyspark-client-rust installs the same
pyspark API surface backed by the native Rust engine (tonic). Because it
installs under the `pyspark` import name as a drop-in for the reference
pyspark-client, it should be easy to tell -- at runtime and on PyPI -- which
client is in use, so behavior and bug reports are attributed to the right
project.
This adds:
- Runtime identity markers: pyspark.__rust_client__ (True) and
pyspark.__engine__ ("rust").
- A one-time INFO log on first session connect identifying the Rust-backed
client.
- A "Which client am I using?" docs page (pyspark vs pyspark-client vs
pyspark-client-rust, how to tell them apart, where to file issues, server
compatibility), linked from the docs home and the Compatibility page.
- Sharpened PyPI metadata (description, keywords, Documentation URL).
Follow-up from the dev@ discussion on the Python wrapper of the Rust Connect
client.
> Make the active Spark Connect client identifiable (pyspark-client-rust vs the
> reference client)
> -----------------------------------------------------------------------------------------------
>
> Key: SPARK-59136
> URL: https://issues.apache.org/jira/browse/SPARK-59136
> Project: Spark
> Issue Type: Improvement
> Components: Connect
> Affects Versions: 5.0.0
> Reporter: Hyukjin Kwon
> Priority: Major
> Labels: pull-request-available
>
> Alongside the Rust Spark Connect client, pyspark-client-rust installs the
> same pyspark API surface backed by the native Rust engine (tonic). Because it
> installs under the `pyspark` import name as a drop-in for the reference
> pyspark-client, it should be easy to tell - at runtime, on PyPI, and in the
> docs - which client is in use, so behavior and bug reports are attributed to
> the right project.
> This adds:
> - Runtime identity markers: pyspark.__rust_client__ (True) and
> pyspark.__engine__ ("rust").
> - A one-time INFO log on first session connect identifying the Rust-backed
> client.
> - A "Which client am I using?" docs page (pyspark vs pyspark-client vs
> pyspark-client-rust, how to tell them apart, where to file issues, server
> compatibility), linked from the docs home and the Compatibility page.
> - Install/uninstall guidance: because all three packages share the `pyspark`
> import directory, the Installation docs spell out that you must uninstall the
> existing client before installing (not on top of it), and that uninstalling
> pyspark-client-rust alone leaves no working pyspark - you must reinstall
> pyspark-client/pyspark to switch back.
> - Sharpened PyPI metadata (description, keywords, Documentation URL).
> Follow-up from the dev@ discussion on the Python wrapper of the Rust Connect
> client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
