sentry-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arjun Mishra (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SENTRY-1896) Optimize retrieving entities by other entity types
Date Tue, 21 Aug 2018 19:07:00 GMT

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

Arjun Mishra updated SENTRY-1896:
---------------------------------
    Attachment: SENTRY-1896.11.patch

> Optimize retrieving entities by other entity types
> --------------------------------------------------
>
>                 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
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: SENTRY-1896.01.patch, SENTRY-1896.02.patch, SENTRY-1896.03.patch,
SENTRY-1896.04.patch, SENTRY-1896.05.patch, SENTRY-1896.06.patch, SENTRY-1896.07.patch, SENTRY-1896.08.patch,
SENTRY-1896.09.patch, SENTRY-1896.10.patch, SENTRY-1896.11.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. 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
(v7.6.3#76005)

Mime
View raw message