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-339) Remove PrivilegeName column and constructPrivilegeName() function
Date Thu, 17 Jul 2014 20:05:07 GMT

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

SentryQA commented on SENTRY-339:
---------------------------------

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

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

{color:red}ERROR:{color} failed to build with patch (exit code 134)

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

This message is automatically generated.

> 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