hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-5928) Add a hive authorization plugin api that does not assume privileges needed
Date Thu, 16 Jan 2014 08:47:19 GMT


Hive QA commented on HIVE-5928:

{color:green}Overall{color}: +1 all checks pass

Here are the results of testing the latest attachment:

{color:green}SUCCESS:{color} +1 4929 tests passed

Test results:
Console output:

Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.


> Add a hive authorization plugin api that does not assume privileges needed
> --------------------------------------------------------------------------
>                 Key: HIVE-5928
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Authorization
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>         Attachments: HIVE-5928.1.patch, HIVE-5928.2.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

View raw message