Hi - thanks for the background.
One last question (promise) - if I'm also going to connect to Impala on either the Quickstart VM or an EC2 install (using Cloudera's ODBC drivers for Impala), should I also connect using port 10000, i.e. the Hiveserver2 port? Or should I use 21050?
Reason I ask is that now testing the Impala drivers, 10000 works, but I can't get a connection to work on 21050 (although I seem to remember it worked on that port before...)
You should use port 21050 to connect to Impala, as long as that port hasn't changed in your settings. You should choose no authentication if you do not have security setup on EC2/Quickstart.
Glad to see the HS2 connection is up and running!
Thanks. One other issue I hit with Impala is that, on the EC2 install, the port isn't open (21050); this looks like it's because the maximum number of security rules in an AWS security group has been exceeded by the installer. You can add more security groups to an instance, so I'll try that route.
I am encountering issues as well.
Using the cloudera quickstart VM - NAT networking with port forwarding. Have included port 10000.
Managed to connect pentaho kettle to hive. I have an install of both tableau 32 bit and 64 bit.
Have followed the instructions above, starting up hiveserver2 etc, however I still get this error:
Driver Version: V184.108.40.2061
Running connectivity tests...
Failed to establish connection
SQLSTATE: HY000[Cloudera][Hardy] (34) Error from Hive: Bad version identifier.
TESTS COMPLETED WITH ERROR.
I am running CDH 4.4...is this an issue? Anyone know how to solve this?
Many thanks in advance.
I'd guess that your driver and HS2 have a version mismatch. It's not clear from your post exactly what you are using to try to connect to HS2. You said that you got pentaho kettle to connect successfully, and that you have both 32 bit and 64 bit tableau, but not what you used that failed.
You might want to verify the compatibility of your driver with CDH versions (ie check with your driver's vendor), and / or try posting your question in the Hive forums, as this doesn't seem to be an issue with Cloudera Manager.
Hi, sorry to hear you're having problems.
CDH 4.4 should work. I have the CDH4.4 VM running on my laptop with NAT and can connect to it.
Are you choosing an authentication mechanism or leaving it as no authentication?
If you are choosing No Authentication, you will need to disable impersonation for HiveServer2 and add the following to the safety valve for hive-site.xml:
Another option you could try is to leave HiveServer2 as is and choose User Name authentication and supply a user name.
You may also want to try the newest version of the ODBC driver.