drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holger Kiel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5702) Jdbc Driver Class not found
Date Mon, 04 Dec 2017 18:30:00 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277204#comment-16277204
] 

Holger Kiel commented on DRILL-5702:
------------------------------------

Please have a look at file "profile.props" in drill-jdbc-all-1.12.0.jar. This is part of the
content:
{code}
package.namespace.prefix=${package.namespace.prefix}
{code}

When I'm building everything from the repository, my jdbc Driver hat the following instead:
{code}
package.namespace.prefix=oadd.
{code}
The latter works for me.

> Jdbc Driver Class not found
> ---------------------------
>
>                 Key: DRILL-5702
>                 URL: https://issues.apache.org/jira/browse/DRILL-5702
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 1.11.0
>            Reporter: Holger Kiel
>            Assignee: Vitalii Diravka
>            Priority: Blocker
>             Fix For: 1.12.0
>
>
> Cannot connect to drill cluster after upgrade to new Jar drill-jdbc-all-1.11.0.jar. When
replacing Jar file with older release drill-jdbc-all-1.10.0.jar, connection works again. Tested
with various client applications:
> {code}
> java.lang.RuntimeException: java.lang.RuntimeException: java.lang.ClassNotFoundException:
Class ${package.namespace.prefix}org.apache.hadoop.security.JniBasedUnixGroupsMappingWithFallback
not found
>         at oadd.org.apache.hadoop.conf.Configuration.getClass(Configuration.java:2227)
>         at oadd.org.apache.hadoop.security.Groups.<init>(Groups.java:80)
>         at oadd.org.apache.hadoop.security.Groups.<init>(Groups.java:74)
>         at oadd.org.apache.hadoop.security.Groups.getUserToGroupsMappingService(Groups.java:303)
>         at oadd.org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:283)
>         at oadd.org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:311)
>         at oadd.org.apache.drill.exec.rpc.security.plain.PlainFactory.createAndLoginUser(PlainFactory.java:63)
>         at oadd.org.apache.drill.exec.rpc.user.UserClient.authenticate(UserClient.java:244)
>         at oadd.org.apache.drill.exec.rpc.user.UserClient.connect(UserClient.java:171)
>         at oadd.org.apache.drill.exec.client.DrillClient.connect(DrillClient.java:432)
>         at oadd.org.apache.drill.exec.client.DrillClient.connect(DrillClient.java:379)
>         at org.apache.drill.jdbc.impl.DrillConnectionImpl.<init>(DrillConnectionImpl.java:158)
>         at org.apache.drill.jdbc.impl.DrillJdbc41Factory.newDrillConnection(DrillJdbc41Factory.java:72)
>         at org.apache.drill.jdbc.impl.DrillFactory.newConnection(DrillFactory.java:69)
>         at oadd.org.apache.calcite.avatica.UnregisteredDriver.connect(UnregisteredDriver.java:143)
>         at org.apache.drill.jdbc.Driver.connect(Driver.java:72)
>         at java.sql.DriverManager.getConnection(DriverManager.java:664)
>         at java.sql.DriverManager.getConnection(DriverManager.java:208)
> {code}
> Workaround is using the old driver version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message