[
https://issues.apache.org/jira/browse/SENTRY-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725140#comment-16725140
]
Hadoop QA commented on SENTRY-2481:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12952366/SENTRY-2481.2.patch
against master.
{color:red}Overall:{color} -1 due to 4 errors
{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestHMSFollower
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestHMSFollower
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/4299/console
This message is automatically generated.
> Filter HMS server-side objects based on HMS user authorization
> --------------------------------------------------------------
>
> Key: SENTRY-2481
> URL: https://issues.apache.org/jira/browse/SENTRY-2481
> Project: Sentry
> Issue Type: New Feature
> Components: Sentry
> Reporter: Sergio Peña
> Assignee: Sergio Peña
> Priority: Major
> Attachments: SENTRY-2481.1.patch, SENTRY-2481.2.patch
>
>
> Sentry provides a mechanism to filter HMS objects from users who are not
> authorized to view certain objects, but this filter happens on the HMS client
> only. The support for the HMS server-side is needed as there might clients
> who access the server using Thrift API causing this security concern.
>
> To provide with such support. Sentry should re-use the
> SentryMetaStoreFilterHook, which will be called by the HMS server, in order
> to filter the unwanted objects.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
