You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2014/01/15 00:19:24 UTC
[jira] [Work logged] (HIVE-5928) Add a hive authorization plugin
api that does not assume privileges needed
[ https://issues.apache.org/jira/browse/HIVE-5928?focusedWorklogId=15634&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-15634 ]
Thejas M Nair logged work on HIVE-5928:
---------------------------------------
Author: Thejas M Nair
Created on: 14/Jan/14 23:18
Start Date: 14/Jan/14 23:18
Worklog Time Spent: 2h
Issue Time Tracking
-------------------
Worklog Id: (was: 15634)
Time Spent: 2h
Remaining Estimate: 12h (was: 120h)
> Add a hive authorization plugin api that does not assume privileges needed
> --------------------------------------------------------------------------
>
> Key: HIVE-5928
> URL: https://issues.apache.org/jira/browse/HIVE-5928
> Project: Hive
> Issue Type: Sub-task
> Components: Authorization
> Reporter: Thejas M Nair
> Assignee: Thejas M Nair
> Attachments: HIVE-5928.1.patch, hive_auth_class_preview.txt
>
> Original Estimate: 120h
> Time Spent: 2h
> Remaining Estimate: 12h
>
> The existing HiveAuthorizationProvider interface implementations can be used to support custom authorization models.
> But this interface limits the customization for these reasons -
> 1. It has assumptions about the privileges required for an action.
> 2. It does have not functions that you can implement for having custom ways of doing the actions of access control statements.
> This jira proposes a new interface HiveAuthorizer that does not make assumptions of the privileges required for the actions. The authorize() functions will be equivalent of authorize(<operation type>, <input objects>, <output objects>). It will also have functions that will be called from the access control statements.
> The current HiveAuthorizationProvider will continue to be supported for backward compatibility.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)