You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Anastasiia Sergienko (JIRA)" <ji...@apache.org> on 2019/08/16 11:34:00 UTC

[jira] [Created] (DRILL-7353) Found a bug in the JDBC driver drill-jdbc-all-1.16.0.jar

Anastasiia Sergienko created DRILL-7353:
-------------------------------------------

             Summary: Found a bug in the JDBC driver drill-jdbc-all-1.16.0.jar
                 Key: DRILL-7353
                 URL: https://issues.apache.org/jira/browse/DRILL-7353
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 1.16.0, 1.15.0
            Reporter: Anastasiia Sergienko
         Attachments: Screenshot from 2019-08-16 13-26-29.png

Hello. I used a JDBC driver for connection to the Apache Drill and probably found a bug.
My problem was the driver didn't register itself automatically and I needed to use  `Class.forName("org.apache.drill.jdbc.Driver");` in Java.


I opened the jar archive(drill-jdbc-all-1.16.0.jar) and checked the next file: /META-INF/services/java.sql.Driver.
What I found there was: org.apache.calcite.avatica.remote.Driver, which doesn't correspond to the real driver path. I changed the line to: org.apache.drill.jdbc.Driver

After that my problem was solved. I also checked the 1.15.0 version and the path there was the same. Is it supposed to be like that?

 

 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)