Check cluster configuration for Hive and Tez
Check the configuration settings for Hive and Tez in the Ambari UI.
-
Go to Ambari > Services > Hive > CONFIGS > ADVANCED. Make sure that the Hive configurations are as follows:
- hive.hook.proto.base-directory:
{hive_metastore_warehouse_external_dir}/sys.db/query_data/
- hive.exec.failure.hooks:
org.apache.hadoop.hive.ql.hooks.HiveProtoLoggingHook
- hive.exec.post.hooks:
org.apache.hadoop.hive.ql.hooks.HiveProtoLoggingHook
- hive.exec.pre.hooks:
org.apache.hadoop.hive.ql.hooks.HiveProtoLoggingHook
- hive.metastore.transactional.event.listeners:
org.apache.hive.hcatalog.listener.DbNotificationListener
NoteIf you have upgraded your cluster from HDP 2.6.x to HDP 3.1.x, then specifyorg.apache.hive.hcatalog.listener.DbNotificationListener
in the hive.metastore.transactional.event.listeners property under Advanced hivemetastore-site.
- hive.hook.proto.base-directory:
-
Go to Ambari > Services > Tez > CONFIGS > Custom tez-site. Make sure that the Tez configuration is as follows:
- tez.history.logging.service.class:
org.apache.tez.dag.history.logging.proto.ProtoHistoryLoggingService
- tez.history.logging.proto-base-dir:
{hive_metastore_warehouse_external_dir}/sys.db/
- tez.history.logging.service.class: