hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Vary (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19569) alter table db1.t1 rename db2.t2 generates MetaStoreEventListener.onDropTable()
Date Tue, 19 Jun 2018 08:50:00 GMT

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

Peter Vary commented on HIVE-19569:
-----------------------------------

[~maheshk114]: Thanks! Ping me if you need review :D

> 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
>              Labels: pull-request-available
>             Fix For: 3.1.0, 4.0.0
>
>         Attachments: HIVE-19569.01-branch-3.patch, HIVE-19569.01.patch, HIVE-19569.02.patch,
HIVE-19569.03.patch, HIVE-19569.04.patch
>
>
> 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)

Mime
View raw message