You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Rick Hillegas (JIRA)" <ji...@apache.org> on 2015/10/30 23:11:27 UTC
[jira] [Closed] (SPARK-11426) JDBCRDD should use JdbcDialect to
probe for the existence of a table
[ https://issues.apache.org/jira/browse/SPARK-11426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Hillegas closed SPARK-11426.
---------------------------------
Resolution: Not A Problem
I have decided that this issue is not a problem. JDBCRDD.resolveTable() is not probing for the existence of a table. Instead, it is trying to compute the row-signature of an arbitrary query expression. See the discussion on https://github.com/apache/spark/pull/9202
> 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
> Components: SQL
> Affects Versions: 1.5.1
> Reporter: Rick Hillegas
> Priority: Minor
>
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org