sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiaomeng Huang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-339) Remove PrivilegeName column and constructPrivilegeName() function
Date Wed, 23 Jul 2014 03:02:39 GMT

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

Xiaomeng Huang commented on SENTRY-339:
---------------------------------------

Hi, [~arun_suresh]
I have seen dapeng's comment, and you will update your patch to set a composite index for
privilegeName.
But in last patch, I haven't seen it.
Sentry-340 deponds on this patch, could you please update your patch?

> 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
>
>
> 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