Couldn't add a longer reply for some reason so replied as an answer see below. ... View more

Did you try adding /etc/hive/conf, it will be the location where your hive-site.xml is? AFAIK for a single user case you should not need to do anything with UGI object. For a multi-user case, you can do something like: UserGroupInformation ugi = UserGroupInformation.loginUserFromKeytabAndReturnUGI(user, keytabfile); Connection con = (Connection) ugi.doAs(new PrivilegedExceptionAction<Object>() { public Object run() { Connection tcon = null; try { tcon = DriverManager.getConnection(connectionURL, user, passwd); } catch (SQLException e) {} return tcon; } }); Refer to Hive Wiki. ... View more

For a single user case you may not have to do programmatic login, did you try including /etc/hive/conf in the classpath of your Java client? ... View more

Did you do kinit on the shell where you run the Java client from? ... View more

Is the DROP TABLE command hanging or is just outright fails? If its hanging it would be good to see the stack dump from the cli to determine where it hangs. The other option is to manually delete the HDFS directory (recursive remove) of the offending table followed by a drop table if exists <tablename>. ... View more

There is an internal bug that is tracking this at Hortonworks. ... View more

Make sure hbase is installed on the machine where you are running the hive cli from. In presence of hbase install, hive cli automatically includes the required hbase libraries in the classpath. ... View more

Have you followed the instructions from Ambari documentation for configuring Hive view. It states there: Ambari views use the doAs option for commands. This option enables the Ambari process user to impersonate the Ambari logged-in user. To avoid receiving permissions errors for job submissions and file save operations, you must create HDFS users for all Ambari users that use the views. The HDFS permission error that you are showing above: org.apache.hadoop.security.AccessControlException: Permission denied: user=root, access=WRITE, inode="/user/root":hdfs:hdfs:drwxr-xr-x It clearly shows that the /user/root which is the default user home of root user on HDFS is not owned by root, that's a problem. Can you make sure that /user/root is created with ownership of root user. Also if the authorization mode in Hive is StorageBased then /apps/hive/warehouse should be writable by root. This is usually accomplished by having the executing user in the same group as the one that has write permissions on /apps/hive/warehouse. I would also guess that in your current setup any query that requires a job to be run will fail. Simple metadata queries would succeed. ... View more

Could table_name be an external table with location that is readable by admin? ... View more