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

Ramesh Mani updated RANGER-3407:
--------------------------------
    Description: 
Handle  authorization of Hive Drop database / table if exists in 
RangerHiveAuthorizer when database / table doesn't exists. When Database or 
table doesn't exist there is no input/output HivePrivilege Object present in 
the authorization request and hence there will be exception because of the 
checks introduced in  RANGER-3148.

This has to be handled in the same way how HIVE handles when "drop 
database/table if exists" is run on database / table which are not present.

  was:
Handle Hive Drop database / table if exists in RangerHiveAuthorizer when 
database / table doesn't exists. When Database or table doesn't exist there is 
no input/output HivePrivilege Object present in the authorization request and 
hence there will be exception because of the checks introduced in  RANGER-3148.

This has to be handled in the same way how HIVE handles when "drop 
database/table if exists" is run on database / table which are not present.


> Handle authorization of Hive Drop database / table if exists in 
> RangerHiveAuthorizer when database / table doesn't exist 
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-3407
>                 URL: https://issues.apache.org/jira/browse/RANGER-3407
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>    Affects Versions: 3.0.0, 2.2.0
>            Reporter: Ramesh Mani
>            Assignee: Ramesh Mani
>            Priority: Major
>             Fix For: 3.0.0, 2.2.0
>
>
> Handle  authorization of Hive Drop database / table if exists in 
> RangerHiveAuthorizer when database / table doesn't exists. When Database or 
> table doesn't exist there is no input/output HivePrivilege Object present in 
> the authorization request and hence there will be exception because of the 
> checks introduced in  RANGER-3148.
> This has to be handled in the same way how HIVE handles when "drop 
> database/table if exists" is run on database / table which are not present.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to