You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by gatorsmile <gi...@git.apache.org> on 2016/07/20 05:44:03 UTC

[GitHub] spark pull request #14086: [SPARK-16463][SQL] Support `truncate` option in O...

Github user gatorsmile commented on a diff in the pull request:

    https://github.com/apache/spark/pull/14086#discussion_r71468419
  
    --- Diff: sql/core/src/main/scala/org/apache/spark/sql/DataFrameWriter.scala ---
    @@ -419,8 +422,13 @@ final class DataFrameWriter[T] private[sql](ds: Dataset[T]) {
           }
     
           if (mode == SaveMode.Overwrite && tableExists) {
    -        JdbcUtils.dropTable(conn, table)
    -        tableExists = false
    +        if (extraOptions.getOrElse("truncate", "false").toBoolean &&
    +            JdbcUtils.isCascadingTruncateTable(url) == Some(false)) {
    +          JdbcUtils.truncateTable(conn, table)
    --- End diff --
    
    If `truncateTable` failed due to a non fatal exception, should we fall back to the previous way (i.e., drop and create)? This is a design decision. CC @srowen @rxin 


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

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