You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2018/06/04 18:21:01 UTC
[jira] [Commented] (HIVE-19569) alter table db1.t1 rename db2.t2
generates MetaStoreEventListener.onDropTable()
[ https://issues.apache.org/jira/browse/HIVE-19569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500670#comment-16500670 ]
Thejas M Nair commented on HIVE-19569:
--------------------------------------
Patch for HIVE-19488 addresses this.
> alter table db1.t1 rename db2.t2 generates MetaStoreEventListener.onDropTable()
> -------------------------------------------------------------------------------
>
> Key: HIVE-19569
> URL: https://issues.apache.org/jira/browse/HIVE-19569
> Project: Hive
> Issue Type: Bug
> Components: Metastore, Standalone Metastore, Transactions
> Affects Versions: 3.0.0
> Reporter: Eugene Koifman
> Assignee: mahesh kumar behera
> Priority: Major
>
> 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]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)