Github user brandonJY commented on a diff in the pull request:
https://github.com/apache/spark/pull/20325#discussion_r162781167
--- Diff: docs/sql-programming-guide.md ---
@@ -580,6 +580,9 @@ default local Hive metastore (using Derby) for you.
Unlike the `createOrReplaceT
Hive metastore. Persistent tables will still exist even after your Spark
program has restarted, as
long as you maintain your connection to the same metastore. A DataFrame
for a persistent table can
be created by calling the `table` method on a `SparkSession` with the name
of the table.
+Notice that for `DataFrames` is built on Hive table, `insertInto` should
be used instead of `saveAsTable`.
--- End diff --
@gatorsmile Could you elaborate on your comment? The purpose of this
sentence was to warn user to use `insertInto` when they are dealing DataFrames
that created from Hive table. Since due to
https://issues.apache.org/jira/browse/SPARK-16803, `saveAsTable` will not work
on that special case. Or do you have any suggestions to make it more clear?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
