-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[PySpark] Add blanklines to Python docstrings so example code renders correctly #1808
Conversation
Can one of the admins verify this patch? |
Jenkins, add to whitelist. |
Jenkins, test this please. |
LGTM and waiting for Jenkins ... Does it include all occurrences? |
I looked through the .py files in the pyspark and pyspark/mllib directories and didn't find any others. |
QA tests have started for PR 1808. This patch merges cleanly. |
QA results for PR 1808: |
@rnowling Thanks for checking all py files! I've merged this into both master and branch-1.1. |
… correctly Author: RJ Nowling <[email protected]> Closes #1808 from rnowling/pyspark_docs and squashes the following commits: c06d774 [RJ Nowling] Add blanklines to Python docstrings so example code renders correctly (cherry picked from commit e537b33) Signed-off-by: Xiangrui Meng <[email protected]>
… correctly Author: RJ Nowling <[email protected]> Closes apache#1808 from rnowling/pyspark_docs and squashes the following commits: c06d774 [RJ Nowling] Add blanklines to Python docstrings so example code renders correctly
… to 3.4) (apache#1808) * rdar://111235765 ALTER TABLE ... WRITE command (apache#1231) (apache#1466) This PR cherry-picks the command to set write distribution and ordering in a table. These changes are needed to allow customers to control the required distribution and ordering in Iceberg. It adds a new command that will be only supported by the Iceberg data source. This PR comes with tests. * rdar://84102488 Support ordering and distribution during table creation (apache#1485) This PR cherry-picks the ordering and distribution during table creation to 3.2. The same syntax is supported in 3.0 and 3.1. These changes are needed to define a sort key and distribution in Iceberg tables. Yes but the changes won't affect anyone except Iceberg users. This PR comes with tests. Co-authored-by: Russell Spitzer <[email protected]> Co-authored-by: Anton Okolnychyi <[email protected]>
No description provided.