[ 
https://issues.apache.org/jira/browse/SENTRY-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arjun Mishra updated SENTRY-1947:
---------------------------------
    Description: 
Right now when roles a re set current, we do nothing to optimize requesting for 
privileges. We basically get all roles, and then use the intersection to 
further filter the roles. After which we get privileges. 
There should be a better approach to this. We should simply use those current 
roles, and return privileges for them. We don't even need to check if the 
current roles belong to the groups because that is something that should've 
been checked earlier when making roles current

  was:
Right now when roles a re set current, we do nothing to optimize requesting for 
privileges. We basically get all roles, and then use the intersection to 
further filter the roles. After which we get privileges. 
There should be a better approach to this. When should simply use those current 
roles, and return privileges for them. We don't even need to check if the 
current roles belong to the groups because that is something that should've 
been checked earlier when making roles current


> Leverage Current Roles to speed up requests for privileges
> ----------------------------------------------------------
>
>                 Key: SENTRY-1947
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1947
>             Project: Sentry
>          Issue Type: Improvement
>          Components: Sentry
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Right now when roles a re set current, we do nothing to optimize requesting 
> for privileges. We basically get all roles, and then use the intersection to 
> further filter the roles. After which we get privileges. 
> There should be a better approach to this. We should simply use those current 
> roles, and return privileges for them. We don't even need to check if the 
> current roles belong to the groups because that is something that should've 
> been checked earlier when making roles current



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to