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

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

Commit eb97c746d2309fcf78ff3b50751cd5e27101539a in impala's branch 
refs/heads/master from Fredy Wijaya
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=eb97c74 ]

IMPALA-8293 (Part 2): Add support for Ranger cache invalidation

This patch adds support for Ranger cache invalidation via INVALIDATE
METADATA and REFRESH AUTHORIZATION. This patch introduces a new catalog
object type called AUTHZ_CACHE_INVALIDATION to allow broadcasting
messages from Catalogd to Impalads to update their local Ranger caches.
For better user experience, every GRANT/REVOKE statement will invalidate
the Ranger authorization cache.

Testing:
- Replaced the sleep in test_ranger.py with INVALIDATE METADATA or
  REFRESH AUTHORIZATION
- Ran all FE tests
- Ran all E2E authorization tests

Change-Id: Ia7160c082298e0b8cc2742dd3facbd4978581288
Reviewed-on: http://gerrit.cloudera.org:8080/13134
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]

Reply via email to