obelix74 commented on PR #3523: URL: https://github.com/apache/polaris/pull/3523#issuecomment-3802433362
> @obelix74 @singhpk234 : WDYT about starting an RFC doc + `dev` thread on this? I believe a structured overview of this feature would be good to set the stage for PRs :) (apologies if I missed it) I am trying to solve two sets of asks from my product folks with this. 1. Metrics - what tables were accessed by a client principal 2. Auditing - which user accessed what data and why From the metrics perspective, today, with `1.3.0`, I want to be able to report on table metrics based on: Track table scan operations: - by table - by snapshot - by time range - by realm - by user principal - by engine For commit report queries: - by operation type - data growth - file churn - storage analysis Also many operational dashboards, and filtering by user, realm, engine name, version etc. I have not thought about roles in this flow at all, perhaps it will be useful. @singhpk234 recommended adding roles and I added them. I normalized the roles tables from a RDBMS perspective, but I didn't realize there are other similar fields stored as JSON already. -- 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]
