[SPARK-12579] User-specified JDBC driver should always take precedence

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.1, 2.0.0
• Component/s: SQL
• Target Version/s: 2.0.0
• Assignee: Josh Rosen
• Reporter: Josh Rosen
• Created: 30/Dec/15 03:18
• Updated: 06/May/16 14:57
• Resolved: 04/Jan/16 18:39

Description

Spark SQL's JDBC data source allows users to specify an explicit JDBC driver to load using the driver argument, but in the current code it's possible that the user-specified driver will not be used when it comes time to actually create a JDBC connection.

In a nutshell, the problem is that you might have multiple JDBC drivers on your classpath that claim to be able to handle the same subprotocol and there doesn't seem to be an intuitive way to control which of those drivers takes precedence.

Issue Links

• is duplicated by: SPARK-12563 "No suitable driver" when calling JdbcUtils.saveTable in isolation
• links to: [Github] Pull Request #10519 (JoshRosen)