Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

Cloudera Impala ODBC on RHEL Linux

avatar
New Contributor

I’ve installed the Cloudera ODBC driver on our AWS LINUX. I am following all the instructions in the associated guide and after configuring the odbc.ini as follows:

 

[ODBC Data Sources]

CDLPROD DSN=Cloudera ODBC Driver for Impala 64-bit

CDLQA   DSN=Cloudera ODBC Driver for Impala 64-bit

 

[CDLPROD]

Driver=/opt/cloudera/impalaodbc/lib/64/libclouderaimpalaodbc64.so

Host=edlimpalaprod.jnj.com

Port=21050

AuthMech=3

UseSASL=1

TrustedCerts=/opt/cloudera/impalaodbc/lib/64/cacerts.pem

UID=sagbcsbp@JNJ.COM

PWD=XXXXXX

TSaslTransportBufSize = 1000

 

 

[CDLQA]

Driver=/opt/cloudera/impalaodbc/lib/64/libclouderaimpalaodbc64.so

Host=edlimpalaqa.jnj.com

Port=21050

AuthMech=3

UseSASl=1

TrustedCerts=/opt/cloudera/impalaodbc/lib/64/cacerts.pem

UID=sagbcsbq@JNJ.COM

PWD=XXXXXX

TSaslTransportBufSize = 1000

 

I am trying to test the DSN connection using the following command from /usr/local/odbc:

 

isql -v CDLPROD

[S1000][unixODBC][Cloudera][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect.

[ISQL]ERROR: Could not SQLConnect

 

Would someone be able to help me resolve this issue? It would be greatly appreciated.

 

 

3 REPLIES 3

avatar
Expert Contributor

Hi @mrmikewhitman,

Based on the error message it appears to be a certification issue. I would start by verifying if the certificate is valid with openssl and check if it works with impala-shell to connect to Impala.

Additionally, with a proxy installed there are further requirements, please see them here.

avatar
New Contributor

I am having the same trouble here.

impala-shell -i my_host_url:21050

Answer:

Starting Impala Shell without Kerberos authentication
Opened TCP connection to my_hot_url:21050
Error connecting: TTransportException, TSocket read 0 bytes
Kerberos ticket found in the credentials cache, retrying the connection with a secure transport.
Error connecting: TTransportException, Could not start SASL: Error in sasl_client_start (-4) SASL(-4): no mechanism available: No worthy mechs found

I am not sure how to proceed.

Any suggestion?

 

Thank you 🙂

 

avatar
Cloudera Employee

Hello there,

 

I am Pradheep, it seems currently you are experiencing two problems.

 

1. From AWS Linux host, you are unable to connect Impala daemon and getting SSL related error.

2. In Impala-Shell, also you are unable to connect.

 

For Impala-shell, instead of "impala-shell -i my_host_url:21050" command, I recommend you to check with CM > Impala > Connection String example command and share the result here.

 

Based on the output, we will check for SSL issue with ODBC driver.