You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Endre Kovacs (JIRA)" <ji...@apache.org> on 2017/08/21 15:08:00 UTC

[jira] [Commented] (RANGER-1631) create temp function failing with permission issues

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

Endre Kovacs commented on RANGER-1631:
--------------------------------------

created unit test for this issue
please review @ https://reviews.apache.org/r/61783/

> create temp function failing with permission issues
> ---------------------------------------------------
>
>                 Key: RANGER-1631
>                 URL: https://issues.apache.org/jira/browse/RANGER-1631
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 1.0.0, master
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>             Fix For: 1.0.0, 0.7.2
>
>
> create temp function failing with permission issues, even when the policy is maintained for database=*, table=*, column=*. Reason being Hive didn't send database name. In earlier version, this was working because resource match did check for the hierarchy relation for the resource, not in current version we do the check and this is causing the issue
> SOLUTION: When create function is done and when database is null we need to make the database="" so the check for hierarchy passes and policy get evaluated. This is a workaround to avoid regression and actual fix has to be done in HIVE , for which there is already a bug raised.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)