sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sravya Tirukkovalur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-339) Remove PrivilegeName column and constructPrivilegeName() function
Date Fri, 25 Jul 2014 00:26:39 GMT

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

Sravya Tirukkovalur commented on SENTRY-339:
--------------------------------------------

@Arun, looks like the pre commit build has some failures. Pre commit is a bit flaky in terms
of resources(https://issues.apache.org/jira/browse/SENTRY-344), but above once are functional
failures. Can you please take a look? Thanks! Also I think we should hold on to push this
change to release 1.4.0 until we test it out on all backend dbs. What do you think?

> Remove PrivilegeName column and constructPrivilegeName() function
> -----------------------------------------------------------------
>
>                 Key: SENTRY-339
>                 URL: https://issues.apache.org/jira/browse/SENTRY-339
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: db_policy_store
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>         Attachments: SENTRY-339.1.patch, SENTRY-339.2.patch, SENTRY-339.3.patch, SENTRY-339.4.patch
>
>
> The {{privilegeName}} column in the Privilege table was initially created to enforce
uniqueness of Privileges with same server+db+table+uri+action. This can be done using composite
unique key constraint in the underlying db.
> It would also cleanup the Sentry Store codebase a bit.. 



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

Mime
View raw message