[jira] [Commented] (SPARK-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006463#comment-15006463 ] somil deshmukh commented on SPARK-10946: create new pull request with new changes in some scala classes. https://github.com/apache/spark/pull/9733 > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15006461#comment-15006461 ] Apache Spark commented on SPARK-10946: -- User 'somideshmukh' has created a pull request for this issue: https://github.com/apache/spark/pull/9733 > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989353#comment-14989353 ] Apache Spark commented on SPARK-10946: -- User 'somideshmukh' has created a pull request for this issue: https://github.com/apache/spark/pull/9465 > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14989356#comment-14989356 ] somil deshmukh commented on SPARK-10946: https://github.com/apache/spark/pull/9465 here is new pull request > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984935#comment-14984935 ] somil deshmukh commented on SPARK-10946: https://github.com/somideshmukh/spark-master-1.5.1/pull/2 Is this fine now. > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14984995#comment-14984995 ] Sean Owen commented on SPARK-10946: --- No, you are still opening PRs versus your own fork. Have a look at git / github tutorials and the contributing link above. > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982138#comment-14982138 ] somil deshmukh commented on SPARK-10946: I would like to work on this .pls assign to me > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982140#comment-14982140 ] somil deshmukh commented on SPARK-10946: Pull request is https://github.com/somideshmukh/spark-master-1.5.1/commit/820f8e2b3c9a75b42234d7be6b799a7d8ed059de > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982224#comment-14982224 ] Sean Owen commented on SPARK-10946: --- [~somi...@us.ibm.com] you just need to open a pull request https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982328#comment-14982328 ] somil deshmukh commented on SPARK-10946: https://github.com/somideshmukh/spark-master-1.5.1/pull/1 > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
[ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14982506#comment-14982506 ] Sean Owen commented on SPARK-10946: --- That is not a pull request opened vs apache/master though. You made a pull request against your own fork. > JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate > for DDLs > -- > > Key: SPARK-10946 > URL: https://issues.apache.org/jira/browse/SPARK-10946 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 1.4.0, 1.4.1, 1.5.1 >Reporter: Pallavi Priyadarshini >Priority: Minor > > Certain DataFrame APIs invoke DDLs such as CREATE TABLE and DROP TABLE under > the covers. Current code in DataFrameWriter and JDBCUtils uses > PreparedStatement.executeUpdate to issue the DDLs to the DBs. This causes the > DDLs to fail against couple of databases that do not support prepares of DDLs. > Can we use Statement.executeUpdate instead of > PreparedStatement.executeUpdate? DDL is not a repetitive activity, so there > shouldn't be a performance impact. > I can submit a PULL request if no one has objections. > Thanks. -- 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
