You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sentry.apache.org by "guoquan (JIRA)" <ji...@apache.org> on 2015/03/18 06:14:42 UTC
[jira] [Updated] (SENTRY-594) Alter database should check output
privilege instead of input
[ https://issues.apache.org/jira/browse/SENTRY-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
guoquan updated SENTRY-594:
---------------------------
Fix Version/s: 1.5.0
> Alter database should check output privilege instead of input
> -------------------------------------------------------------
>
> Key: SENTRY-594
> URL: https://issues.apache.org/jira/browse/SENTRY-594
> Project: Sentry
> Issue Type: Bug
> Reporter: Xiaomeng Huang
> Assignee: Xiaomeng Huang
> Fix For: 1.5.0
>
> Attachments: SENTRY-594.001.patch
>
>
> "ALTER DATABASE" command can get entities from WriteEntity, and get nothing from ReadEntity. So this command should check output privilege instead of input.
> What's more, "ALTER TABLE" also check output privilege, likes below:
> {code}
> HiveAuthzPrivileges alterTablePrivilege = new HiveAuthzPrivileges.AuthzPrivilegeBuilder().
> addOutputObjectPriviledge(AuthorizableType.Table, EnumSet.of(DBModelAction.ALTER)).
> setOperationScope(HiveOperationScope.TABLE).
> setOperationType(HiveOperationType.DDL).
> build();
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)