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

Hadoop QA commented on SENTRY-2144:
-----------------------------------

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

{color:green}Overall:{color} +1 all checks pass

{color:green}SUCCESS:{color} all tests passed

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

This message is automatically generated.

> Alter Table Rename Command should work when table is moved to another database
> ------------------------------------------------------------------------------
>
>                 Key: SENTRY-2144
>                 URL: https://issues.apache.org/jira/browse/SENTRY-2144
>             Project: Sentry
>          Issue Type: Bug
>            Reporter: Na Li
>            Assignee: Na Li
>            Priority: Major
>         Attachments: SENTRY-2144.001.patch, SENTRY-2144.002.patch, 
> SENTRY-2144.003.patch, SENTRY-2144.004.patch
>
>
> Right now, when renaming a table, if the database changes, the privileges 
> will be moved to the wrong table.
> For example, original table is db1.tbl1, and user changes to db2.tbl2 using 
> command 
> ALTER TABLE [old_db_name.]old_table_name RENAME TO 
> [new_db_name.]new_table_name
>  *Expected behavior*:
>  The privileges associated with db1.tbl1 should be removed from db1.tbl1, and 
> added to *{color:#205081}db2{color}*.tbl2.
> *Actual behavior*:
>  The privileges associated with db1.tbl1 is removed from db1.tbl1, and added 
> to {color:#FF0000}*db1*{color}.tbl2.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to