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

Arjun Mishra updated SENTRY-1896:
---------------------------------
    Description: 
Right now when we get privileges from sentry, we pass in a provider like set of 
groups. Then we create a MSentryGroup object for each group and then get roles 
using the .getRoles() method. However, DataNucleus takes too long and the fetch 
doesn't seem to be lazy. This is bad since we only need the "Role Names" for 
the group and not the entire Role object.  
Instead running a SQL like query and just getting roleNames will drastically 
improve performance

  was:
Right now when we get privileges from sentry, we pass in a provider like set of 
groups. Then we create a MSentryGroup object and then get roles using the 
.getRoles() method. However, DataNucleus takes too long and the fetch doesn't 
seem to be lazy. This is bad since we only need the "Role Names" for the group 
and not the entire Role object.  
Instead running a SQL like query and just getting roleNames will drastically 
improve performance


> Optimize retrieving roles for groups
> ------------------------------------
>
>                 Key: SENTRY-1896
>                 URL: https://issues.apache.org/jira/browse/SENTRY-1896
>             Project: Sentry
>          Issue Type: Improvement
>          Components: Sentry
>    Affects Versions: 2.0.0
>            Reporter: Arjun Mishra
>            Assignee: Arjun Mishra
>             Fix For: 2.0.0
>
>
> Right now when we get privileges from sentry, we pass in a provider like set 
> of groups. Then we create a MSentryGroup object for each group and then get 
> roles using the .getRoles() method. However, DataNucleus takes too long and 
> the fetch doesn't seem to be lazy. This is bad since we only need the "Role 
> Names" for the group and not the entire Role object.  
> Instead running a SQL like query and just getting roleNames will drastically 
> improve performance



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

Reply via email to