[
https://issues.apache.org/jira/browse/DRILL-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130644#comment-15130644
]
Vincent Uribe commented on DRILL-3161:
--------------------------------------
I tried adding the java.sql.Driver file myself to the drill-jdbc-all-1.4.0.jar
with no luck. the file is present but the driver doest not seem to load. Any
inputs?
> Drill JDBC driver not visible/auto-registered via Service Provider Mechanism
> ----------------------------------------------------------------------------
>
> 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)
> Fix For: Future
>
>
> 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}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
