Thanks for the response. I tried disabling Atlas (and only Atlas) in Ambari as admin. Afterward, I tried executing any Hive query through both Ambari or Beeline. In both cases I get an error: Error: Error while processing statement: FAILED: Hive Internal Error: com.sun.jersey.api.client.ClientHandlerException(java.io.IOException: java.net.ConnectException: Connection refused) (state=08S01,code=12) It seems Hive and Atlas are tightly coupled. Working against any sort of "dummy database" causes an error in the Atlas bridge which propagates up to Hive. Example: 8: jdbc:hive2://localhost:10000> select count(1);
INFO : Tez session hasn't been created yet. Opening session
INFO : Dag name: select count(1)(Stage-1)
INFO :
INFO : Status: Running (Executing on YARN cluster with App id application_1465411333149_0001)
INFO : Map 1: -/-Reducer 2: 0/1
INFO : Map 1: 0/1Reducer 2: 0/1
INFO : Map 1: 0(+1)/1Reducer 2: 0/1
INFO : Map 1: 1/1Reducer 2: 0(+1)/1
INFO : Map 1: 1/1Reducer 2: 1/1
Error: Error while processing statement: FAILED: Hive Internal Error: java.lang.NullPointerException(null) (state=08S01,code=12)
8: jdbc:hive2://localhost:10000> select 1;
Error: Error while processing statement: FAILED: Hive Internal Error: java.lang.NullPointerException(null) (state=08S01,code=12)
... View more
