Feedback
Did this article resolve your question/issue?

   

Article

Socket closed error occurs connecting to Apache Hive while using Kerberos

Information

 
TitleSocket closed error occurs connecting to Apache Hive while using Kerberos
URL NameSocket-closed-error-occurs-connecting-to-Apache-Hive-while-using-Kerberos
Article Number000183007
EnvironmentProduct: Connect for ODBC Apache Hive driver
Version: 7.1
OS: All supported platforms
Database: Apache Hive
Application: All supported applications
Question/Problem Description
Socket closed error occurs connecting to Apache Hive while using Kerberos with the Connect for ODBC Apache Hive driver.
Steps to Reproduce
Clarifying Information
The SASL QoP is set to “auth-conf”
Error MessageERROR: CLI error trying to establish connection:[DataDirect][ODBC Apache Hive Wire Protocol driver]Socket closed.)
Defect Number
Enhancement Number
Cause
The SASL QoP setting “auth-conf” is currently NOT supported. The ODBC driver currently only supports a SASL QoP setting of "auth".
Resolution
Configure the Hive server to use SASL QoP setting of "auth".

If the environment must use SASL QoP setting “auth-conf” consider opening a driver enhancement to add this functionality. For additional information, see KB article 10839  How to submit an idea for a Progress product enhancement .
Workaround
Notes
Last Modified Date4/13/2017 4:15 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.