sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SentryQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-136) Thrift request structs should include the groupName in addition to the userName
Date Wed, 12 Mar 2014 23:39:43 GMT

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

SentryQA commented on SENTRY-136:
---------------------------------

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

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

{color:red}ERROR:{color} failed to apply patch (exit code 1):
The patch does not appear to apply with p0, p1, or p2



Console output: http://bigtop01.cloudera.org:8080/job/PreCommit-SENTRY-Build/32/console

This message is automatically generated.

> Thrift request structs should include the groupName in addition to the userName
> -------------------------------------------------------------------------------
>
>                 Key: SENTRY-136
>                 URL: https://issues.apache.org/jira/browse/SENTRY-136
>             Project: Sentry
>          Issue Type: Sub-task
>            Reporter: Shreepadma Venugopalan
>            Assignee: Shreepadma Venugopalan
>         Attachments: SENTRY-136.patch, SENTRY-136.patch
>
>
> Today, thrift request structs use the userName of the user on whose behalf the request
is performed. Instead, we should include the list of groups to which the user belongs. Benefits,
> a) user-group resolution can be restricted to the client i.e., impala, hs2, solr etc
and hence sentry service doesn't have to resolve the mapping.
> b) user-group mapping doesn't have to present on the node that's hosting the sentry service.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message