[
https://issues.apache.org/jira/browse/SENTRY-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045686#comment-14045686
]
SentryQA commented on SENTRY-315:
---------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12652775/SENTRY-315.1.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.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
{color:red}ERROR:{color} Failed:
org.apache.sentry.provider.db.service.persistent.TestSentryStore
Console output:
http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/193/console
This message is automatically generated.
> SHOW CURRENT ROLE fails if the one of the groups doesn't have any roles
> granted
> -------------------------------------------------------------------------------
>
> Key: SENTRY-315
> URL: https://issues.apache.org/jira/browse/SENTRY-315
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Prasad Mujumdar
> Assignee: Prasad Mujumdar
> Fix For: 1.4.0
>
> Attachments: SENTRY-315.1.patch
>
>
> In case of 'SET ROLE' and 'SHOW CURRENT ROLE' sentry client tries to get all
> the roles available to the current user. The server resolves all the groups
> that the user belongs to, and then list all roles granted for each of these
> groups. The problem is that if one of the groups is not granted any roles,
> then the underlying SentryStore API throws NoSuchObject exception. This is
> propagated back to the client.
> In cases like 'SET ROLE' and 'SHOW CURRENT ROLE', we need to ignore this
> exception and continue collecting roles.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
