[jira] [Updated] (SPARK-16463) Support `truncate` option in Overwrite mode for JDBC DataFrameWriter
[ https://issues.apache.org/jira/browse/SPARK-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-16463: -- Component/s: SQL > Support `truncate` option in Overwrite mode for JDBC DataFrameWriter > - > > Key: SPARK-16463 > URL: https://issues.apache.org/jira/browse/SPARK-16463 > Project: Spark > Issue Type: Improvement > Components: SQL >Reporter: Dongjoon Hyun >Assignee: Dongjoon Hyun >Priority: Minor > Fix For: 2.1.0 > > > This issue adds a boolean option, `truncate`, for SaveMode.Overwrite of JDBC > DataFrameWriter. If this option is `true`, it use `TRUNCATE TABLE` instead of > `DROP TABLE`. > - Without CREATE/DROP privilege, we can save dataframe to database. Sometime > these are not allowed for security. > - It will keep the existing table information, so users can add and keep some > additional CONSTRAINTs for the table. > - Sometime, TRUNCATE is faster than the combination of DROP/CREATE. > This issue is different from SPARK-16410 which aims to use `TRUNCATE` only > for JDBC sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-16463) Support `truncate` option in Overwrite mode for JDBC DataFrameWriter
[ https://issues.apache.org/jira/browse/SPARK-16463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Owen updated SPARK-16463: -- Assignee: Dongjoon Hyun > Support `truncate` option in Overwrite mode for JDBC DataFrameWriter > - > > Key: SPARK-16463 > URL: https://issues.apache.org/jira/browse/SPARK-16463 > Project: Spark > Issue Type: Improvement >Reporter: Dongjoon Hyun >Assignee: Dongjoon Hyun >Priority: Minor > Fix For: 2.1.0 > > > This issue adds a boolean option, `truncate`, for SaveMode.Overwrite of JDBC > DataFrameWriter. If this option is `true`, it use `TRUNCATE TABLE` instead of > `DROP TABLE`. > - Without CREATE/DROP privilege, we can save dataframe to database. Sometime > these are not allowed for security. > - It will keep the existing table information, so users can add and keep some > additional CONSTRAINTs for the table. > - Sometime, TRUNCATE is faster than the combination of DROP/CREATE. > This issue is different from SPARK-16410 which aims to use `TRUNCATE` only > for JDBC sources. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org