I think I'm running into a very similar issue that the poster above is running into. Only in our current environment we're using Hiverserver 2 in Zookeeper dynamic allocation, in a Kerborized environement.
When I implement my connection string to hive I'm using the following example:
jdbc:hive2://<FQDN_Zookeeper>:2181,<FQDN_Zookeeper>:2181,<FQDN_Zookeeper>:2181/;serviceDiscoveryMode=zooKeeper;principal=hive/_HOST@<DOMAIN>;zooKeeperNamespace=hiveserver2-binary
When it tries to connect I get a GSS error.
What I've narrowed down is that when I get this error it's because Toad is not handling the "_HOST" when making the connection string.
When I change the principal=hive/<FQDN_HIVESERVER>@<DOMAIN> I'm able to successfully connect to Hiveserver2.
Now where I run into an ultimate problem. While using: jdbc:hive2://<FQDN_Zookeeper>:2181,<FQDN_Zookeeper>:2181,<FQDN_Zookeeper>:2181/;serviceDiscoveryMode=zooKeeper;principal=hive/<FQDN_HIVESERVER_1>@<DOMAIN>;zooKeeperNamespace=hiveserver2-binary
I'm only attaching to <FQDN_HIVESERVER_1> and when it goes down I'm not longer able to connect because I'm now passing the incorrect Kerberos Principal to <FQDN_HIVESERVER_2>. As soon as I manually switch over my connection string I'm able to connect to FQDN_HIVESERVER_2, but if that server goes down I'm not having to manually edit my connection strings each time I want to connect if I have an issue. Which I think defeats the purpose of HA.
Has anyone been able to get Toad to pass either the _HOST or know how to configured it to work with JDBC Hiveserver2 HA with Zookeeper?
Thanks.