Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/16352
---
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
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16352#discussion_r93390578
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/api/r/SQLUtils.scala
---
@@ -276,11 +276,12 @@ private[sql] object SQLUtils extends Logging {
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/16352#discussion_r93388755
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/api/r/SQLUtils.scala
---
@@ -276,11 +276,12 @@ private[sql] object SQLUtils extends Logging {
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16352#discussion_r93385438
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/api/r/SQLUtils.scala
---
@@ -276,11 +276,12 @@ private[sql] object SQLUtils extends Logging {
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/16352#discussion_r93300223
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/SQLContext.scala ---
@@ -747,7 +747,7 @@ class SQLContext private[sql](val sparkSession:
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/16352
[SPARK-18947][SQL] SQLContext.tableNames should not call Catalog.listTables
## What changes were proposed in this pull request?
It's a huge waste to call `Catalog.listTables` in
