You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Fredy Wijaya (JIRA)" <ji...@apache.org> on 2019/06/17 19:07:00 UTC

[jira] [Updated] (IMPALA-8671) Do not re-create a new instance of AuthorizationChecker with Ranger authorization

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

Fredy Wijaya updated IMPALA-8671:
---------------------------------
    Priority: Critical  (was: Major)

> Do not re-create a new instance of AuthorizationChecker with Ranger authorization
> ---------------------------------------------------------------------------------
>
>                 Key: IMPALA-8671
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8671
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Frontend
>            Reporter: Fredy Wijaya
>            Assignee: Fredy Wijaya
>            Priority: Critical
>
> RangerAuthorizationChecker is stateless unlike SentryAuthorizationChecker. However, in some cases, we always re-create a new instance of RangerAuthorizationChecker due to the logic here: https://github.com/apache/impala/blob/3bd53972cec3b8a863075cb2344115a950be848a/fe/src/main/java/org/apache/impala/service/Frontend.java#L290-L293. This causes the plugin to be re-initialized, which can be expensive. The solution is to reuse the same RangerAuthorizationChecker instance.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org