[GitHub] spark pull request #16588: [SPARK-19092] [SQL] [Backport-2.1] Save() API of ...

[gatorsmile]

Github user gatorsmile closed the pull request at:

https://github.com/apache/spark/pull/16588


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

[GitHub] spark pull request #16588: [SPARK-19092] [SQL] [Backport-2.1] Save() API of ...

[gatorsmile]

GitHub user gatorsmile opened a pull request:

https://github.com/apache/spark/pull/16588

[SPARK-19092] [SQL] [Backport-2.1] Save() API of DataFrameWriter should not 
scan all the saved files #16481

### What changes were proposed in this pull request?

 This PR is to backport https://github.com/apache/spark/pull/16481 to 
Spark 2.1
--- 
`DataFrameWriter`'s [save() 
API](https://github.com/gatorsmile/spark/blob/5d38f09f47a767a342a0a8219c63efa2943b5d1f/sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala#L207)
 is performing a unnecessary full filesystem scan for the saved files. The 
save() API is the most basic/core API in `DataFrameWriter`. We should avoid it. 

### How was this patch tested?
Added and modified the test cases

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gatorsmile/spark backport-19092

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/spark/pull/16588.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 #16588


commit a246ae9ce329518f4e97f7b8ca67446ba72af2f1
Author: gatorsmile 
Date:   2017-01-15T19:25:40Z

backport




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org