[jira] [Commented] (SENTRY-550) SentryStore support more actions for rename

["Hadoop QA (JIRA)" <ji...@apache.org>]

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

Hadoop QA commented on SENTRY-550:
----------------------------------

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

{color:red}Overall:{color} -1 due to 2 errors

{color:red}ERROR:{color} mvn test exited 1
{color:red}ERROR:{color} Failed: org.apache.sentry.provider.db.service.persistent.TestSentryStore

Console output: https://builds.apache.org/job/PreCommit-SENTRY-Build/79/console

This message is automatically generated.

> SentryStore support more actions for rename
> -------------------------------------------
>
>                 Key: SENTRY-550
>                 URL: https://issues.apache.org/jira/browse/SENTRY-550
>             Project: Sentry
>          Issue Type: Sub-task
>            Reporter: Xiaomeng Huang
>            Assignee: Xiaomeng Huang
>         Attachments: SENTRY-550.001.patch
>
>
> Currently if we rename table, SentryStore just rename ALL, INSERT and SELECT from this role. But now we support more actions, so we should support more actions for rename. If we don't rename privilege with all action, it actually is a bug in some cases, e.g.
> {code}
> >grant select, insert, alter, drop to table db1.tb1
> >grant create  to database db1
> >rename tb1 to tb2
> >drop tb2 -->should be success
> >drop tb1 -->should be failed
> {code}
> Like the use case above, if we rename tb1, we should have drop permission on tb2, and no permission to drop tb1
> But before this patch, 'drop tb2' will failed, and 'drop tb1' will success



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)