[HIVE-19569] alter table db1.t1 rename db2.t2 generates MetaStoreEventListener.onDropTable()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0, 4.0.0-alpha-1
• Component/s: Metastore, Standalone Metastore, Transactions
• Labels: pull-request-available
• Target Version/s: 3.1.0, 4.0.0
• Assignee: mahesh kumar behera
• Reporter: Eugene Koifman
• Created: 16/May/18 03:40
• Updated: 21/Oct/22 06:59
• Resolved: 18/Jun/18 20:38

Description

When renaming a table within the same DB, this operation causes MetaStoreEventListener.onAlterTable() to fire but when changing DB name for a table it causes MetaStoreEventListener.onDropTable() + MetaStoreEventListener.onCreateTable().
The files from original table are moved to new table location.
This creates confusing semantics since any logic in onDropTable() doesn't know about the larger context, i.e. that there will be a matching onCreateTable().

In particular, this causes a problem for Acid tables since files moved from old table use WriteIDs that are not meaningful with the context of new table.

Current implementation is due to replication. This should ideally be changed to raise a "not supported" error for tables that are marked for replication.

cc sankarh

Issue Links

• Is contained by: HIVE-19488 Enable CM root based on db parameter, identifying a db as source of replication.
• is related to: HIVE-18748 Rename table impacts the ACID behavior as table names are not updated in meta-tables.
• is related to: HIVE-19488 Enable CM root based on db parameter, identifying a db as source of replication.
• links to: GitHub Pull Request #368
• links to: GitHub Pull Request #368