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

Posted to commits@sentry.apache.org by "Xiaomeng Huang (JIRA)" <ji...@apache.org> on 2014/12/10 07:26:12 UTC

[jira] [Updated] (SENTRY-541) UdfUri privilege should use itself's privilege instead of anyPrivilege

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

Xiaomeng Huang updated SENTRY-541:
----------------------------------
    Summary: UdfUri privilege should use itself's privilege instead of anyPrivilege  (was: UdfUri privilege should use itself's privilege rather than anyPrivilege)

> UdfUri privilege should use itself's privilege instead of anyPrivilege
> ----------------------------------------------------------------------
>
>                 Key: SENTRY-541
>                 URL: https://issues.apache.org/jira/browse/SENTRY-541
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Xiaomeng Huang
>            Assignee: Xiaomeng Huang
>         Attachments: SENTRY-541.001.patch
>
>
> Currently both 'use db' and 'create function' use anyPrivilege, I think 'create funciton' can own itself's privilege which operation scope is ‘URI’ rather than 'CONNECT'. Because the test case in TestHiveAuthzBindings.testValidateCreateFunctionForAdmin make me very confused, we must have column level privilege so that we can pass the authorize. And this jira also block SENTRY-505.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)