You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2017/05/16 08:50:04 UTC

[jira] [Created] (HIVE-16676) RENAME TABLE and RENAME PARTITION events shall be modified as DROP+CREATE events.

Sankar Hariappan created HIVE-16676:
---------------------------------------

             Summary: RENAME TABLE and RENAME PARTITION events shall be modified as DROP+CREATE events.
                 Key: HIVE-16676
                 URL: https://issues.apache.org/jira/browse/HIVE-16676
             Project: Hive
          Issue Type: Sub-task
          Components: repl
    Affects Versions: 2.1.0
            Reporter: Sankar Hariappan
            Assignee: Sankar Hariappan


Currently, RENAME TABLE and RENAME PARTITION events are treated as ALTER events. 
For bootstrap dump, if the table is renamed after fetching the table names, then new table will be missing in the dump and so the target database doesn't have both old and new table. During incremental replication, later RENAME events will be noop as the old table doesn't exist in target.
In order to make RENAME replication simple, it is suggested to treat RENAME as DROP+CREATE event.
EVENT_RENAME_TABLE = EVENT_DROP_TABLE + EVENT_CREATE_TABLE.
EVENT_RENAME_PARTITION = EVENT_DROP_PARTITION + EVENT_ADD_PARTITION.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)