[
https://issues.apache.org/jira/browse/DRILL-7353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911384#comment-16911384
]
ASF GitHub Bot commented on DRILL-7353:
---------------------------------------
agozhiy commented on issue #1845: DRILL-7353: Wrong driver class is written to
the java.sql.Driver
URL: https://github.com/apache/drill/pull/1845#issuecomment-523029588
@arina-ielchiieva, There are two artifacts that provide java.sql.Driver to
the jar. Apparently the wrong one overwrites the right. So I excluded the file
from Avatica to resolve the conflict.
Initially I tried to combine the files into one so both Avatica and Drill
jdbc drivers were contained in java.sql.Driver. But as Avatica driver itself is
not present in the final jar, error occurred during initialization and so no
drivers were registered automatically at all. It can be fixed if swap driver
names in java.sql.Driver, but this is unacceptable.
The best solution would be to include the file from a specific artifact and
exclude all the others but I couldn't find a way to do so. But I agree that the
current approach is not safe. I'll need to look into it a bit more.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Wrong driver class is written to the java.sql.Driver
> ----------------------------------------------------
>
> Key: DRILL-7353
> URL: https://issues.apache.org/jira/browse/DRILL-7353
> Project: Apache Drill
> Issue Type: Bug
> Affects Versions: 1.15.0, 1.16.0
> Reporter: Anastasiia Sergienko
> Assignee: Anton Gozhiy
> Priority: Major
> Fix For: 1.17.0
>
> 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
(v8.3.2#803003)
