You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by Stephan202 <gi...@git.apache.org> on 2018/02/03 13:29:59 UTC
[GitHub] spark pull request #20057: [SPARK-22880][SQL] Add cascadeTruncate option to ...
Github user Stephan202 commented on a diff in the pull request:
https://github.com/apache/spark/pull/20057#discussion_r165814475
--- Diff: docs/sql-programming-guide.md ---
@@ -1339,6 +1339,13 @@ the following case-insensitive options:
This is a JDBC writer related option. When <code>SaveMode.Overwrite</code> is enabled, this option causes Spark to truncate an existing table instead of dropping and recreating it. This can be more efficient, and prevents the table metadata (e.g., indices) from being removed. However, it will not work in some cases, such as when the new data has a different schema. It defaults to <code>false</code>. This option applies only to writing.
</td>
</tr>
+
+ <tr>
+ <td><code>cascadeTruncate</code></td>
+ <td>
+ This is a JDBC writer related option. If enabled and supported by the JDBC database (PostgreSQL and Oracle at the moment), this options allows execution of a <code>TRUNCATE TABLE t CASCADE</code>. This will affect other tables, and thus should be used with case. This option applies only to writing.
--- End diff --
About the documentation: `s/used with case/used with care/`
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org