spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-10946) JDBC - Use Statement.executeUpdate instead of PreparedStatement.executeUpdate for DDLs
Date Mon, 02 Nov 2015 10:02:27 GMT

    [ https://issues.apache.org/jira/browse/SPARK-10946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message