You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@sentry.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2014/05/26 19:10:01 UTC

[jira] [Updated] (SENTRY-234) Allow Sentry service to accept Server/Db/Table/URI in the listPrivileges API

     [ https://issues.apache.org/jira/browse/SENTRY-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arun Suresh updated SENTRY-234:
-------------------------------

    Attachment: SENTRY-234.1.patch

Attaching Patch :
* Added new API to list privileges based on Db/Table name or URI
* Added test cases

> Allow Sentry service to accept Server/Db/Table/URI in the listPrivileges API
> ----------------------------------------------------------------------------
>
>                 Key: SENTRY-234
>                 URL: https://issues.apache.org/jira/browse/SENTRY-234
>             Project: Sentry
>          Issue Type: New Feature
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: SENTRY-234.1.patch
>
>
> Currently a client of the Sentry Service has to get all the privileges for a role and filter at the Client side.
> This fix would allow push down of fields such as server/URI/Db and table name so the filtering can happen at the Server Side



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