hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (HIVE-19569) alter table db1.t1 rename db2.t2 generates MetaStoreEventListener.onDropTable()
Date Tue, 16 Jun 2020 16:55:02 GMT


ASF GitHub Bot logged work on HIVE-19569:

                Author: ASF GitHub Bot
            Created on: 16/Jun/20 16:54
            Start Date: 16/Jun/20 16:54
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on pull request #368:

   This pull request has been automatically marked as stale because it has not had recent
activity. It will be closed if no further activity occurs.
   Feel free to reach out on the list if the patch is in need of reviews.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

Issue Time Tracking

            Worklog Id:     (was: 446698)
    Remaining Estimate: 0h
            Time Spent: 10m

> alter table db1.t1 rename db2.t2 generates MetaStoreEventListener.onDropTable()
> -------------------------------------------------------------------------------
>                 Key: HIVE-19569
>                 URL:
>             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
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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

View raw message