Additional configuration tasks
Make sure you consider these additional configurations as part of your DAS installation.
- Work with HiveServer2: If your Hive deployment is not LLAP-enabled and does not have
Hive Server Interactive, you need to update the configuration for DAS to work with HiveServer 2
as follows:
Go to
and changeuse.hive.interactive.mode=true
touse.hive.interactive.mode=false
-
Cleanup of Audit Log: Audit Log is written by Hive/Tez to HDFS for DAS to consume. Once DAS consumes them, this information on HDFS is no longer required. They are cleaned automatically via a thread in HMS (Hive metastore).
The time to live count of the audit logs is defined in the
hive.hook.proto.events.ttl
parameter. By default, the logs are retained for seven days. To configure a custom value:-
On the Ambari UI, go to
and specify the time to live in thehive.hook.proto.events.ttl
parameter.For example, to retain the logs for 30 days, specify 30d.
Typically, a 30-day duration is useful if you want to download older DAG data.
- Restart Hive service.
-