[jira] [Commented] (SPARK-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347700#comment-16347700 ] Tony Xu commented on SPARK-19209: - This seems like a forgotten issue but I'm still experiencing it in Spark 2.2.1 Could this issue be related to the Driver itself? For example, I tried using the MySQL JDBC driver and that seems to work fine on the first try. However, when I try using Snowflake's JDBC driver, I run into this exact issue. I'm not sure what the difference between these two drivers are but it might be worth digging into > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos >Priority: Critical > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834103#comment-15834103 ] Xiao Li commented on SPARK-19209: - Based on my understanding, the problem is java.sql.DriverManager class that can't access drivers loaded by Spark ClassLoader. I just submitted the PR. The changes made in the PR does not sounds a solution for the reported issue. It could be caused by the other code changes in 2.1 that change the current ClassLoader [~darabos] Could you just make a try and see whether the revert made in the PR resolves your issue? Thanks! > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos >Priority: Critical > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15834100#comment-15834100 ] Apache Spark commented on SPARK-19209: -- User 'gatorsmile' has created a pull request for this issue: https://github.com/apache/spark/pull/16678 > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos >Priority: Critical > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826547#comment-15826547 ] Xiao Li commented on SPARK-19209: - I will submit a PR to fix it soon. Thanks! > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824224#comment-15824224 ] Daniel Darabos commented on SPARK-19209: Sorry, Jira had some issues when I was trying to file this issue; I guess it resulted in the duplicates. Also it says I'm watching the issue, but I got no mail about your comments. (I checked my spam folder.) Well I have unwatched and watched it now, hope it helps. Yes, it is the same if the table exists: {verbatim} scala> spark.read.format("jdbc").option("url", "jdbc:sqlite:testdb").option("dbtable", "y").load.show java.sql.SQLException: No suitable driver at java.sql.DriverManager.getDriver(DriverManager.java:315) at org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) at org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) at scala.Option.getOrElse(Option.scala:121) at org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) at org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) at org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) at org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) ... 48 elided scala> spark.read.format("jdbc").option("url", "jdbc:sqlite:testdb").option("dbtable", "y").load.show +-+ |value| +-+ |1| |2| |3| |4| |5| |6| |7| |8| |9| | 10| +-+ {verbatim} If I specify the driver class ({{.option("driver", "org.sqlite.JDBC")}}) then there is no problem: the method works on the first try. Subsequent tries work even if the driver is not specified. This is not a silver bullet, as our JDBC path typically comes from an external source (i.e. the user). But this is definitely a workaround when working in the shell. Thanks! > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@
[jira] [Commented] (SPARK-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1584#comment-1584 ] Xiao Li commented on SPARK-19209: - This could be caused by the classLoader issue. Anyway, let me first move the driverClass initialization back to createConnectionFactory. Thanks! > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822201#comment-15822201 ] Xiao Li commented on SPARK-19209: - I am trying to find a workaround for your case. Could you add an extra option {{.option("driver", "com.mysql.jdbc.Driver")}} in your code? Note, I do not have your class name. Could you replace it by your class name in the option? > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822186#comment-15822186 ] Xiao Li commented on SPARK-19209: - Did you also hit the same exception `java.sql.SQLException: No suitable driver` when the table exists? > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822154#comment-15822154 ] Xiao Li commented on SPARK-19209: - Thanks for reporting the regression. Let me take a look at this. > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822145#comment-15822145 ] Xiao Li commented on SPARK-19209: - It sounds like you create multiple duplicate JIRAs: SPARK-19204, SPARK-19205 and SPARK-19209. Let me close the last two. > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars org.xerial.sqlite-jdbc-3.8.11.2.jar > --driver-class-path org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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-19209) "No suitable driver" on first try
[ https://issues.apache.org/jira/browse/SPARK-19209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15821578#comment-15821578 ] Daniel Darabos commented on SPARK-19209: Puzzlingly this only happens in the application when the SparkSession is created with {{enableHiveSupport}}. I guess in {{spark-shell}} it is enabled by default. > "No suitable driver" on first try > - > > Key: SPARK-19209 > URL: https://issues.apache.org/jira/browse/SPARK-19209 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.1.0 >Reporter: Daniel Darabos > > This is a regression from Spark 2.0.2. Observe! > {code} > $ ~/spark-2.0.2/bin/spark-shell --jars > stage/lib/org.xerial.sqlite-jdbc-3.8.11.2.jar --driver-class-path > stage/lib/org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > This is the "good" exception. Now with Spark 2.1.0: > {code} > $ ~/spark-2.1.0/bin/spark-shell --jars > stage/lib/org.xerial.sqlite-jdbc-3.8.11.2.jar --driver-class-path > stage/lib/org.xerial.sqlite-jdbc-3.8.11.2.jar > [...] > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: No suitable driver > at java.sql.DriverManager.getDriver(DriverManager.java:315) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions$$anonfun$7.apply(JDBCOptions.scala:84) > at scala.Option.getOrElse(Option.scala:121) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:83) > at > org.apache.spark.sql.execution.datasources.jdbc.JDBCOptions.(JDBCOptions.scala:34) > at > org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider.createRelation(JdbcRelationProvider.scala:32) > at > org.apache.spark.sql.execution.datasources.DataSource.resolveRelation(DataSource.scala:330) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:152) > at org.apache.spark.sql.DataFrameReader.load(DataFrameReader.scala:125) > ... 48 elided > scala> spark.read.format("jdbc").option("url", > "jdbc:sqlite:").option("dbtable", "x").load > java.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (no such > table: x) > {code} > Simply re-executing the same command a second time "fixes" the {{No suitable > driver}} error. > My guess is this is fallout from https://github.com/apache/spark/pull/15292 > which changed the JDBC driver management code. But this code is so hard to > understand for me, I could be totally wrong. > This is nothing more than a nuisance for {{spark-shell}} usage, but it is > more painful to work around for applications. -- 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