flyrain commented on code in PR #3724:
URL: https://github.com/apache/polaris/pull/3724#discussion_r2800818065
##########
polaris-core/src/main/java/org/apache/polaris/core/auth/PolarisAuthorizableOperation.java:
##########
@@ -144,7 +145,7 @@ public enum PolarisAuthorizableOperation {
DROP_VIEW(VIEW_DROP),
VIEW_EXISTS(VIEW_LIST),
RENAME_VIEW(VIEW_DROP, EnumSet.of(VIEW_LIST, VIEW_CREATE)),
- REPORT_METRICS(EnumSet.noneOf(PolarisPrivilege.class)),
+ REPORT_METRICS(TABLE_REPORT_METRICS),
Review Comment:
In terms of metrics consuming, I don't think it is necessary tied to
read/write. For metrics consuming, we could still have table level privilege
with the combination of namespace-level and catalog-level consuming privileges,
most use cases will be covered. For example, a user granted catalog-level
consuming privilege can see all metrics under the catalog.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
