[ 
https://issues.apache.org/jira/browse/IMPALA-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16584919#comment-16584919
 ] 

ASF subversion and git services commented on IMPALA-7343:
---------------------------------------------------------

Commit 0a901fcb275058fc4c24e243d2a829dfddfef4d5 in impala's branch 
refs/heads/master from [~fredyw]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=0a901fc ]

IMPALA-7343: Update SentryProxy to use Sentry bulk API

Prior to this patch, every Sentry policy update required a Thrift call
to Sentry to get the role privileges per role. This is inefficient.
This patch updates the way Impala update its Sentry policy by using the
new Sentry APIs for getting all roles/users and their associated
privileges in a single Thrift call to Sentry. This patch also updates
SentryProxy to get user privileges.

Before:
- Refreshing 100 roles: 493ms
- Refreshing 1000 roles: 4668ms
- Refreshing 10000 roles: 45636ms

After:
- Refreshing 100 roles: 114ms
- Refreshing 1000 roles: 1021ms
- Refreshing 10000 roles: 10076ms

Testing:
- Ran all FE tests
- Ran all E2E authorization tests

Change-Id: I3ab215f2a5c5111bf1d25eec7fac90506d2f6304
Reviewed-on: http://gerrit.cloudera.org:8080/11250
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Change Sentry proxy to use the bulk API
> ---------------------------------------
>
>                 Key: IMPALA-7343
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7343
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Frontend
>    Affects Versions: Impala 3.0
>            Reporter: Adam Holley
>            Assignee: Fredy Wijaya
>            Priority: Major
>              Labels: security
>
> Currently, Impala makes a thrift call for each role to get privileges.  This 
> will change to get all privileges in one thrift call.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to