We use the Cloudera ODBC Driver for Impala and Cloudera ODBC Driver for Hive inside a service. The service uses a DSN-less connection strings with UseKeytab to authenticate. We do not perform any ticket management, we leave this down to the ODBC driver.   We have observed that connections to hive do not renew the TGT, and will reuse an existing service ticket (expected behaviour).   However, Impala connections renew the TGT on every connection (thus destroying all service tickets..) Impala Service tickets never get reused and the ticket cache is always destroyed. This has to be a bug.   To reproduce.. Open ODBC Administrator and create a DSN connection to an Impala Server with kerberos keytab authentication. Test the connection run klist to show tickets Test the connection again run klist to show the tickets have been renewed ... View more

We use the Cloudera ODBC Driver for Impala from c# .Net using an OdbcConnection.  We are using MIT Kerberos on Windows and keytab authentication.  Occasionally, the process begins throwing the bellow Exception.  Over time, the exception seems to correct itself, however the only known fix to us is to restart the process (which is a problem..)   Exception: [Cloudera][ThriftExtension] (3) Error occurred while contacting server: ETIMEDOUT. The connection has been configured to use a SASL mechanism for authentication. This error might be due to the server is not using SASL for authentication.   Connection String: Driver={Cloudera ODBC Driver for Impala};Host=[ImpalaHostName];Port=21050;AuthMech=1;KrbRealm=[KerberosRealm];KrbServiceName=impala;UseKeytab=1;KrbFQDN=_HOST;UID=[UserName];UPNKeytabMappingFile=[jsonKeyTabMappingFile];UseNativeQuery=1;CurrentSchemaRestrictedMetadata=1;Schema=[Database];SocketTimeout=120   We have also occasionally seen the bellow exception, but these seem to be intermittent. [Cloudera][ImpalaODBC] (450) Error when calling the Impala Thrift API ExecuteStatement: ETIMEDOUT ... View more