[
https://issues.apache.org/jira/browse/HIVE-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106234#comment-14106234
]
Ashu Pachauri commented on HIVE-6250:
-------------------------------------
Oh, I think I should have been more clear in my comment. We have Hive 0.13.1
deployment that we upgraded from Hive 0.12 (used Hive upgrade script). A user
creates a table and then tries to delete the table, the operation fails with
error "No Drop Privileges found" .
The user can grant the privileges to himself explicitly, and then it works.
I am not sure if this is the change, or it is a problem in the upgrade. I just
inferred it from the code changes I saw in this change.
> sql std auth - view authorization should not underlying table. More tests and
> fixes.
> ------------------------------------------------------------------------------------
>
> Key: HIVE-6250
> URL: https://issues.apache.org/jira/browse/HIVE-6250
> Project: Hive
> Issue Type: Sub-task
> Components: Authorization
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Fix For: 0.13.0
>
> Attachments: HIVE-6250.1.patch, HIVE-6250.2.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> This patch adds more tests for table and view authorization and also fixes a
> number of issues found during testing -
> - View authorization should happen on only on the view, and not the
> underlying table (Change in ReadEntity to indicate if it is a direct/indirect
> dependency)
> - table owner in metadata should be the user as per SessionState
> authentication provider
> - added utility function for finding the session state authentication
> provider user
> - authorization should be based on current roles
> - admin user should have all permissions
> - error message improvements
--
This message was sent by Atlassian JIRA
(v6.2#6252)
