You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2014/05/05 20:55:14 UTC
[jira] [Commented] (SENTRY-189) Impala's Invalidate Metadata should
require less privileges
[ https://issues.apache.org/jira/browse/SENTRY-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989840#comment-13989840 ]
Gwen Shapira commented on SENTRY-189:
-------------------------------------
Was convince that "invalidate metadata <table>" is good enough.
Closing this.
> Impala's Invalidate Metadata should require less privileges
> -----------------------------------------------------------
>
> Key: SENTRY-189
> URL: https://issues.apache.org/jira/browse/SENTRY-189
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Gwen Shapira
>
> Right now, Impala's "invalidate metadata" is only available to users with "server" privilege.
> The problem is that "invalidate metadata" has to run every time any change to the data is made. So everyone who has any privilege to write / modify any table in any DB has to be able to invalidate metadata.
> With current privilege model, they need to call an admin to invalidate metadata before they can view data they just loaded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)