GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/14288
[SPARK-16651][PYSPARK][DOC] Make `withColumnRenamed` description more
consistent with Scala API
## What changes were proposed in this pull request?
`withColumnRenamed` is a no-op if the given column name does not exists.
Python documentation also describe that, but this PR adds more explicit line
consistently with Scala to reduce the ambiguity.
```
"""Returns a new :class:`DataFrame` by renaming an existing column.
+ This is a no-op if schema doesn't contain the column name `existing`.
:param existing: string, name of the existing column to rename.
:param col: string, new name of the column.
```
## How was this patch tested?
It's about docs.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dongjoon-hyun/spark SPARK-16651
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/14288.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #14288
----
commit f3a3f8cd694f4e71f791129724927f7316de39a1
Author: Dongjoon Hyun <[email protected]>
Date: 2016-07-20T17:56:52Z
[SPARK-16651][PYSPARK][DOC] Make `withColumnRenamed` description more
consistent with Scala API.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
