[jira] [Commented] (SPARK-16402) JDBC source: Implement save API
[ https://issues.apache.org/jira/browse/SPARK-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786114#comment-15786114 ] Xiao Li commented on SPARK-16402: - Yes. > JDBC source: Implement save API > --- > > Key: SPARK-16402 > URL: https://issues.apache.org/jira/browse/SPARK-16402 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.0.0 >Reporter: Xiao Li > > Currently, we are unable to call the `save` API of `DataFrameWriter` when the > source is JDBC. For example, > {noformat} > df.write > .format("jdbc") > .option("url", url1) > .option("dbtable", "TEST.TRUNCATETEST") > .option("user", "testUser") > .option("password", "testPass") > .save() > {noformat} > The error message users will get is like > {noformat} > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > java.lang.RuntimeException: > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > {noformat} > However, the `save` API is very common for all the data sources, like parquet. -- 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] [Commented] (SPARK-16402) JDBC source: Implement save API
[ https://issues.apache.org/jira/browse/SPARK-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15785990#comment-15785990 ] Nicholas Chammas commented on SPARK-16402: -- [~JustinPihony], [~smilegator] - Does the resolution on SPARK-14525 also resolve this issue? > JDBC source: Implement save API > --- > > Key: SPARK-16402 > URL: https://issues.apache.org/jira/browse/SPARK-16402 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.0.0 >Reporter: Xiao Li > > Currently, we are unable to call the `save` API of `DataFrameWriter` when the > source is JDBC. For example, > {noformat} > df.write > .format("jdbc") > .option("url", url1) > .option("dbtable", "TEST.TRUNCATETEST") > .option("user", "testUser") > .option("password", "testPass") > .save() > {noformat} > The error message users will get is like > {noformat} > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > java.lang.RuntimeException: > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > {noformat} > However, the `save` API is very common for all the data sources, like parquet. -- 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] [Commented] (SPARK-16402) JDBC source: Implement save API
[ https://issues.apache.org/jira/browse/SPARK-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15454500#comment-15454500 ] Xiao Li commented on SPARK-16402: - : ) Let me ping them. You still can bypass it, right? > JDBC source: Implement save API > --- > > Key: SPARK-16402 > URL: https://issues.apache.org/jira/browse/SPARK-16402 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.0.0 >Reporter: Xiao Li > > Currently, we are unable to call the `save` API of `DataFrameWriter` when the > source is JDBC. For example, > {noformat} > df.write > .format("jdbc") > .option("url", url1) > .option("dbtable", "TEST.TRUNCATETEST") > .option("user", "testUser") > .option("password", "testPass") > .save() > {noformat} > The error message users will get is like > {noformat} > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > java.lang.RuntimeException: > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > {noformat} > However, the `save` API is very common for all the data sources, like parquet. -- 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] [Commented] (SPARK-16402) JDBC source: Implement save API
[ https://issues.apache.org/jira/browse/SPARK-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15449509#comment-15449509 ] Dragisa Krsmanovic commented on SPARK-16402: Any progress on this ? > JDBC source: Implement save API > --- > > Key: SPARK-16402 > URL: https://issues.apache.org/jira/browse/SPARK-16402 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.0.0 >Reporter: Xiao Li > > Currently, we are unable to call the `save` API of `DataFrameWriter` when the > source is JDBC. For example, > {noformat} > df.write > .format("jdbc") > .option("url", url1) > .option("dbtable", "TEST.TRUNCATETEST") > .option("user", "testUser") > .option("password", "testPass") > .save() > {noformat} > The error message users will get is like > {noformat} > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > java.lang.RuntimeException: > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > {noformat} > However, the `save` API is very common for all the data sources, like parquet. -- 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] [Commented] (SPARK-16402) JDBC source: Implement save API
[ https://issues.apache.org/jira/browse/SPARK-16402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365150#comment-15365150 ] Apache Spark commented on SPARK-16402: -- User 'gatorsmile' has created a pull request for this issue: https://github.com/apache/spark/pull/14077 > JDBC source: Implement save API > --- > > Key: SPARK-16402 > URL: https://issues.apache.org/jira/browse/SPARK-16402 > Project: Spark > Issue Type: New Feature > Components: SQL >Affects Versions: 2.0.0 >Reporter: Xiao Li > > Currently, we are unable to call the `save` API of `DataFrameWriter` when the > source is JDBC. For example, > {noformat} > df.write > .format("jdbc") > .option("url", url1) > .option("dbtable", "TEST.TRUNCATETEST") > .option("user", "testUser") > .option("password", "testPass") > .save() > {noformat} > The error message users will get is like > {noformat} > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > java.lang.RuntimeException: > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider does not > allow create table as select. > {noformat} > However, the `save` API is very common for all the data sources, like parquet. -- 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