[
https://issues.apache.org/jira/browse/SENTRY-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Na Li updated SENTRY-2144:
--------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
This fix only handles notification event processing when there is no full
snapshot. The changes related to update to full snapshot is tracked in
"SENTRY-2239 FullUpdateModifier does not handle alter table rename correctly"
The patch 006.patch is the same as 001.patch. I waited for 3 hours and the
build for 006.patch was not done. So I committed the patch 001.patch as its
build was successful and it is the same content as 006.patch
> Table Rename Cross Database should update permission correctly
> ---------------------------------------------------------------
>
> 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, SENTRY-2144.006.patch,
> SENTRY-2144.006.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)
