Created 09-14-2017 08:22 PM
When I give the hive ODBC configuration as follows, I am getting this error:
[Hortonworks][Hardy] (34) Error from server: Bad Status: HTTP/1.1 500 Server Error.
Configuration:
Service discovery mode: No Service Discovery
Host: Knox gateway host
Port: 8443 (Knox port)
Authentication mechanism: Username and Password
Thrift transport: HTTP
Created 09-15-2017 12:06 PM
@Geoffrey Shelton Okot Thanks Geoffrey. I got it to work. Used Kerberos as the authentication mechanism. Hive was expecting a Kerberos ticket from Knox.
@Ajay Thanks. Will try with Zookeeper. Yes, able to connect to Hive via beeline. And I have HTTP as the transport mode.
Created 09-14-2017 09:15 PM
If you cluster is Kerberized you MUST choose under you cluster is Kerberized you MUST choose under Authentication Kerberos ,REALM Host FQDN etc
Created 09-14-2017 09:20 PM
@kerra Check if HiveServer2 you are trying to connect is configured properly in knox. Also check if HiveServer2 is set to
hive.server2.transport.mode=http
If zookeeper hosts are accessible than i will recommend using discovery as it will auto detect port,host and other details. Are you able to connect to hive via beeline?
Created 09-15-2017 12:06 PM
@Geoffrey Shelton Okot Thanks Geoffrey. I got it to work. Used Kerberos as the authentication mechanism. Hive was expecting a Kerberos ticket from Knox.
@Ajay Thanks. Will try with Zookeeper. Yes, able to connect to Hive via beeline. And I have HTTP as the transport mode.
Created 09-15-2017 03:54 PM
Some other steps taken:
1. Create a knox.crt file
2. Place it in the cacerts folder in /etc/pki/java
3. Download this cert to the machine where ODBC needs to be configured.
4. Give this path in the SSL options, in the ODBC configuration and check the 'enable SSL' box.
5. Give Kerberos as authentication mechanism, in the ODBC configuration.
6. Give knox URL and port as the host and port, in the ODBC configuration
Created 09-15-2017 06:10 PM
Was it self signed certificate of CA?