You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/08/22 16:42:00 UTC
[jira] [Commented] (SENTRY-1896) Optimize retrieving roles for
groups
[ https://issues.apache.org/jira/browse/SENTRY-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137041#comment-16137041 ]
Hadoop QA commented on SENTRY-1896:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12883139/SENTRY-1896.01.patch against master.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2
Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/3164/console
This message is automatically generated.
> 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
>
> Attachments: SENTRY-1896.01.patch
>
>
> 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 roleNames 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)