You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Daniel Barclay (Drill) (JIRA)" <ji...@apache.org> on 2015/05/21 00:50:00 UTC

[jira] [Created] (DRILL-3161) Drill JDBC driver not visible/auto-registered via SPM

Daniel Barclay (Drill) created DRILL-3161:
---------------------------------------------

             Summary: Drill JDBC driver not visible/auto-registered via SPM
                 Key: DRILL-3161
                 URL: https://issues.apache.org/jira/browse/DRILL-3161
             Project: Apache Drill
          Issue Type: Bug
          Components: Client - JDBC
            Reporter: Daniel Barclay (Drill)
            Assignee: Daniel Barclay (Drill)


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.
&nbsp;

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}}).







--
This message was sent by Atlassian JIRA
(v6.3.4#6332)