Consolidation of Column-Level Access in Ranger Audit Logs

Feature Request / Improvement

Currently, when a query accesses multiple columns within a table, Trino creates separate Ranger audit log for each column involved in the operation. This granular logging, while detailed, can complicate Ranger audit logs management, particularly when compared to how other query engines might aggregate such access details.

For example, executing identical queries Trino and Impala , the resource paths logged in Ranger checks differ significantly.

Impala: Logs a single, combined resource path for a table access, e.g., audit_logs/hiveserver2/requser,resource,others. This path seems to aggregate various access components.

Trino: Logs separate resource paths for different components of the access. For example, a single table access result in three distinct entries: Resource Path: audit_logs/hiveserver2/requser Resource Path: audit_logs/hiveserver2/resource Resource Path: audit_logs/hiveserver2/others

We request a feature to allow Trino to consolidate column-level access within Ranger audit logs.

Environment Details: Trino Version: 479