[DRILL-3161] Drill JDBC driver not visible/auto-registered via Service Provider Mechanism

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: Future
• Component/s: Client - JDBC
• Assignee: Unassigned
• Reporter: Daniel Barclay
• Created: 20/May/15 22:49
• Updated: 27/Feb/17 17:26
• Resolved: 27/Feb/17 17:26

Description

Drill's JDBC driver is not automatically made visible to JDBC's DriverManager and auto-registered, because it does not use Java's Service Provider Mechanism as specified by JDBC 4.0.

This usually means that instead of just having to put the Drill JDBC driver Jar file on the class path and use a Drill JDBC URL (one starting with "jdbc:drill:"), users also have to configure their tools or code with the name of the Drill driver class.
 

The Drill JDBC driver's Jar file should contain a META-INF/services/java.sql.Driver file that contains a line consisting of the fully qualified name of the Drill JDBC driver class (org.apache.drill.jdbc.Driver).

Issue Links

• duplicates: DRILL-4880 Support JDBC driver registration using ServiceLoader