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

Hadoop QA commented on SENTRY-2483:
-----------------------------------

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

{color:red}Overall:{color} -1 due to 8 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationTogglingConf
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.metastore.TestAuthorizingObjectStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.metastore.TestAuthorizingObjectStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.metastore.TestAuthorizingObjectStore
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA
{color:red}ERROR:{color} Failed: 
org.apache.sentry.tests.e2e.hdfs.TestHDFSIntegrationWithHA

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

This message is automatically generated.

> Implement HMS PreReadEvent support in MetastoreAuthzBinding
> -----------------------------------------------------------
>
>                 Key: SENTRY-2483
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2483
>             Project: Sentry
>          Issue Type: Improvement
>          Components: Sentry
>            Reporter: Sergio Peña
>            Assignee: Sergio Peña
>            Priority: Major
>         Attachments: SENTRY-2483.1.patch
>
>
> MetastoreAuthzBinding has support for all HMS DDL events to verify if a user 
> has the authorization to execute them. However, read event, such as 
> READ_DATABASE and READ_TABLE are not supported.
> We should add support for them so HMS can have read authorization checks too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to