[
https://issues.apache.org/jira/browse/SPARK-11426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated SPARK-11426:
----------------------------------
Issue Type: Bug (was: Improvement)
Changing this to be a bug because this is another SQL injection attack.
> JDBCRDD should use JdbcDialect to probe for the existence of a table
> --------------------------------------------------------------------
>
> Key: SPARK-11426
> URL: https://issues.apache.org/jira/browse/SPARK-11426
> Project: Spark
> Issue Type: Bug
> Affects Versions: 1.5.1
> Reporter: Rick Hillegas
>
> JdbcDialect.getTableExistsQuery() lets us specify which query to use in order
> to probe for the existence of a table. Some JdbcDialects (Postgres and MySQL)
> override the default query used for this purpose. Presumably, we should use
> those preferred overrides every time that Spark probes for the existence of a
> query.
> However, JDBCRDD.resolveTable() has its own, hard-coded query which probes
> for the existence of a table. We should make JDBCRDD.resolveTable() call
> JdbcDialect.getTableExistsQuery() instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
