[
https://issues.apache.org/jira/browse/IMPALA-8293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16823179#comment-16823179
]
ASF subversion and git services commented on IMPALA-8293:
---------------------------------------------------------
Commit 2fdc0a57d1b5ca85e47a4ac7dc955336fda693a6 in impala's branch
refs/heads/master from Fredy Wijaya
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2fdc0a5 ]
IMPALA-8293 (Part 1): Move SentryProxy out of CatalogServiceCatalog
The patch refactors the SentryProxy, which does Sentry cache
invalidation from CatalogServiceCatalog into a Sentry-specific
implementation, i.e. SentryCatalogdAuthorizationManager. This patch
also adds a new method in the AuthorizationManager interface to allow
refreshing authorization for any authorization provider that caches the
authorization metadata.
This patch also contains minor clean-up to address comments in this
abandoned CR: https://gerrit.cloudera.org/c/12748
This patch has no functionality change.
Testing:
- Ran all FE tests
- Ran all E2E authorization tests
Change-Id: I3fa14abb09abfb4aaf6231d35114c0e121d6e568
Reviewed-on: http://gerrit.cloudera.org:8080/13065
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Support for Ranger cache invalidation with INVALIDATE METADATA or REFRESH
> AUTHORIZATION
> ---------------------------------------------------------------------------------------
>
> Key: IMPALA-8293
> URL: https://issues.apache.org/jira/browse/IMPALA-8293
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
> Reporter: Fredy Wijaya
> Assignee: Fredy Wijaya
> Priority: Critical
>
> The purpose of this ticket is to figure out a way to force Ranger cache
> invalidation and hook it into Impala existing statements, such as INVALIDATE
> METADATA and REFRESH AUTHORIZATION.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
