Check cluster configuration for Hive and Tez

Before you add the DAS service to your CDP Private Cloud Base cluster, check the configuration settings for Hive and Tez in the Ambari UI. This can ensure that your queries appear properly when you use DAS.

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
  note
  If you have upgraded your cluster from HDP 2.6.x to CDP Private Cloud Base 7.1.x, then specify org.apache.hive.hcatalog.listener.DbNotificationListener in the hive.metastore.transactional.event.listeners property under Advanced hivemetastore-site.
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/