[ 
https://issues.apache.org/jira/browse/SPARK-62135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-62135.
----------------------------------
    Fix Version/s: connect-rust-4.4.0
       Resolution: Fixed

Issue resolved by pull request 911
[https://github.com/apache/spark-connect-rust/pull/911]

> Give the client of Spark Connect, pyspark.sql.connect.client.core, PySpark's 
> docstrings as help() shows them, and compare the docstrings of every module
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-62135
>                 URL: https://issues.apache.org/jira/browse/SPARK-62135
>             Project: Spark
>          Issue Type: Improvement
>          Components: Connect
>    Affects Versions: 5.0.0
>            Reporter: Hyukjin Kwon
>            Assignee: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: connect-rust-4.4.0
>
>
> help() and inspect.getdoc of the client of Spark Connect in the Python client 
> (pyspark-client-rust), pyspark.sql.connect.client.core (SparkConnectClient, 
> the channel builders, RpcDeadlines and the results of the client), do not 
> show PySpark's docstrings, and the module has a docstring of its own where 
> PySpark's core has none. The runtime docstring golden, which compares the 
> docstrings of the modules of pyspark.sql and pyspark.errors with 
> pyspark-client 4.3.0's, leaves pyspark.sql.connect.client out.
> Expected: the client's classes and members carry PySpark's docstrings, as 
> help() shows them in pyspark-client 4.3.0, and the golden compares the 
> docstrings of every module, pyspark.sql.connect.client included.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to