ODBC Connect from Qlik to Hadoop

[#1]

I am trying to connect Qlik to hadoop (cloudera ODBC Driver for Apache Hive) , but i am facing the following error. could someone suggest how to resolve the issue please.

Error: failed! [cloudera][thriftextension] (14) unexpected response from server during a http connection: connect() failed: errno = 10060.

Looking for your support please to find a solution.

Thanks

[#2]

@MohammedMustaq, Welcome to our community! To help you get the best possible answer, I have tagged in our Hive experts @tjangid @asish  who may be able to assist you further.

Please feel free to provide any additional information or details about your query, and we hope that you will find a satisfactory solution to your question.

[#3]

@MohammedMustaq 

make sure you are using the latest ODBC driver and it's set up as per the article:

https://docs.cloudera.com/documentation/other/connectors/hive-odbc/2-6-16/Cloudera-ODBC-Driver-for-A...

Can you please share your configuration?

Cheers!
Tarun

[#4]

@tj2007  @AviD   @tjangid @asish

installing the latest driver version (2.6.16 ) resolved my issue and we were able to load tables in Qlik. But from today we are having the same issue again.

Error: failed! [cloudera][thriftextension] (14) unexpected response from server during a http connection: connect() failed: errno = 10060.

Thanks

Mustaq

[#5]

Hi @MohammedMustaq ,

Please add the trace level logging to the ODBC connection and share the detailed logs. 

[#6 · Accepted solution]

@MohammedMustaq 

Did you manage to solve this error? We are getting something similar.

[Cloudera][ThriftExtension] (14) Unexpected response from server during a HTTP connection: SSL_read: Interrupted system call.

@tj2007 The connector works on one of our servers with the same code and configs but not the other, We have enabled trace level logging but the error in there is the same as the above and there is no additional information around the error.

We are able to connect to the Hive instance through isql from that server fine. 

We have tried with driver version 2.7.0.1002 and 2.6.16 but still the same issue.

Kind Regards