Created 07-07-2016 06:39 PM
Currently we are using Hive CLI on my cluster,For the security purpose we planned to use "beeline" by disabling "Hive CLI" from the existing cluster. I have added the lines below in hive-env template thru ambari to disable the hive shell
if["$SERVICE"="cli"];then
echo "Sorry! I have disabled hive-shell"
exit1
fi
Once I restarted the hive service I could see 2 CRIT alerts from ambari "Hive Metastore process cannot be determined to be up and listening on the network."
I know that I can revoke execute permission for below file on all hive-clients.
/usr/hdp/current/hive-client/bin/hive
Could someone suggest me the better approach to disable "Hive CLI" .
Created 07-07-2016 06:39 PM
if [ "$SERVICE" = "cli" ] && [ "$USER" != "ambari-qa" ]; then echo "Sorry! hive cli has been disabled for security purpose, please use beeline instead." exit 1 fi
This gives ambari-qa the hive cli access and therefore the hive metastore health check passes.
Created 07-07-2016 06:39 PM
if [ "$SERVICE" = "cli" ] && [ "$USER" != "ambari-qa" ]; then echo "Sorry! hive cli has been disabled for security purpose, please use beeline instead." exit 1 fi
This gives ambari-qa the hive cli access and therefore the hive metastore health check passes.
Created 07-07-2016 09:35 PM
Hi Sandeep,
Thank you very much for the prompt response..
I have added the above lines to hive-env template and restarted the hive services and it worked, the error was disappeared from from ambari.
Connected to beeline thru backend submitted a query and it was executed . but I could see the below error.
ERROR hdfs.KeyProviderCache: Could not find uri with key [dfs.encryption.key.provider.uri] to create a keyProvider !!
Please suggest me on this.
Created 07-07-2016 06:42 PM