[ 
https://issues.apache.org/jira/browse/SENTRY-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235571#comment-14235571
 ] 

Hadoop QA commented on SENTRY-405:
----------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12685321/SENTRY-405.002.patch 
against master.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to build with patch (exit code 1)

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/147/console

This message is automatically generated.

> Adding a general jdo access layer(sentrystore) to support the new 
> authorization model 
> --------------------------------------------------------------------------------------
>
>                 Key: SENTRY-405
>                 URL: https://issues.apache.org/jira/browse/SENTRY-405
>             Project: Sentry
>          Issue Type: Sub-task
>    Affects Versions: 1.5.0
>            Reporter: shenguoquan
>            Assignee: shenguoquan
>         Attachments: SENTRY-405.002.patch, SENTRY-405.patch
>
>
> Currently the sentryStore in Sentry only supports database structure 
> authorize model such as Hive/Impala, in order to support more components like 
> Solr or other no  database authorization
> model component. It needs to create a general store to communicate with 
> outside, the structure of privilege model should be hidden. The general store 
> uses interface to transfer the needed information of privilege, the example 
> codes are as following:
> {code}
> public interface PrivilegeReader {
>   public List<? extends Authorizable> getAuthorizables();
>   public String getAction();
>   public String getComponent();
>   public String getService();
>   public String getScope();
>   public Boolean withGrantOption();
> }
> public interface Authorizable {
>   public String getName();
>   public String getTypeName();
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to