[
https://issues.apache.org/jira/browse/RANGER-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630084#comment-16630084
]
Mehul Parikh commented on RANGER-1631:
--------------------------------------
Committed to
[ranger-0.7|https://github.com/apache/ranger/commit/fdf8551a05cd30bd451d7aa5ee2d0a3f2cce1d19]
> 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
> Priority: Major
> 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
(v7.6.3#76005)
