Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

How to Invoke Impala-shell with LDAP

How to Invoke Impala-shell with LDAP

Explorer

Hi,

 

I have setup LDAP to authenticate AD for Impala. I could able to login with AD credentials with beeline and Impala ODBC driver but i am getting hard time to connect using impala-shell. I am not sure what is worng.

 

Log with Beeline connecting to impald with AD user id and Password

3: jdbc:hive2://192.168.203.131:21050> !connect jdbc:hive2://192.168.203.131:21050
Connecting to jdbc:hive2://192.168.203.131:21050
Enter username for jdbc:hive2://192.168.203.131:21050: user1
Enter password for jdbc:hive2://192.168.203.131:21050: ********
Connected to: Impala (version 2.6.0-cdh5.8.0)
Driver: Hive JDBC (version 1.1.0-cdh5.8.0)
Transaction isolation: TRANSACTION_REPEATABLE_READ

Impala-Shell is failing with LDAP. I am doing anything wrong.

Here is the log for Impala shell

[cloudera@quickstart ~]$ impala-shell -i 192.168.203.131 -l --ssl -u user1
Starting Impala Shell using LDAP-based authentication
SSL is enabled. Impala server certificates will NOT be verified (set --ca_cert to change)
LDAP password for user1:
Error connecting: TTransportException, Could not connect to 192.168.203.131:21000
***********************************************************************************
Welcome to the Impala shell. Copyright (c) 2015 Cloudera, Inc. All rights reserved.
(Impala Shell v2.6.0-cdh5.8.0 (5464d17) built on Thu Jun 16 12:35:00 PDT 2016)

When pretty-printing is disabled, you can use the '--output_delimiter' flag to set
the delimiter for fields in the same row. The default is ','.
***********************************************************************************

 

-Sam

 

 

 

1 REPLY 1

Re: How to Invoke Impala-shell with LDAP

Cloudera Employee

Hi Somu,

 

You indicate that SSL is enabled too. Do you have the correct client side SSL certificates in place?

 

Also, do you see any interesting errors in the logs when you do this?

Don't have an account?
Coming from Hortonworks? Activate your account here