[
https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16275572#comment-16275572
]
Vitalii Diravka commented on DRILL-5702:
----------------------------------------
I have not seen this issue on my env:
Ran driillbit in distributed mode from [Drill-1.12 pre-built
tarball|http://home.apache.org/~arina/drill/releases/1.12.0/rc0/] on centos VM
with mapr-core 5.2.2.
{code}
"a drill in the hand is better than two in the bush"
0: jdbc:drill:> select * from sys.version;
+----------+-------------------------------------------+------------------------------------------------------+----------------------------+-----------------------------+----------------------------+
| version | commit_id |
commit_message | commit_time |
build_email | build_time |
+----------+-------------------------------------------+------------------------------------------------------+----------------------------+-----------------------------+----------------------------+
| 1.12.0 | 1da73aa7c704edbd8b674739aba756651677476f | [maven-release-plugin]
prepare release drill-1.12.0 | 29.11.2017 @ 13:18:01 UTC |
[email protected] | 29.11.2017 @ 13:44:42 UTC |
+----------+-------------------------------------------+------------------------------------------------------+----------------------------+-----------------------------+----------------------------+
1 row selected (1.936 seconds)
{code}
Connected to this drillbit from remote machine using
"drill-jdbc-all-1.12.0.jar" from the same pre-built tarball and ran a simple
query.
I have tried Connecting URL directly to drillbit
*jdbc:drill:schema=dfs;drillbit=node1:31010* and through zookeeper
*jdbc:drill:zk=node1:5181/drill/drillbits1* or *jdbc:drill:zk=node1:5181*
I have gotten the successful result in connecting to 1.10 version drillbit with
new jdbc driver as well.
[~korlawulki] What is the version of Drill on your cluster? Is your cluster
secure? Can you share the configs for jdbc connection from the client-side?
> 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)
