hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sankar Hariappan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-17183) Disable rename operations during bootstrap dump
Date Thu, 17 Aug 2017 16:37:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-17183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sankar Hariappan updated HIVE-17183:
------------------------------------
    Description: 
Currently, bootstrap dump shall lead to data loss when any rename happens while dump in progress.

*Scenario:*
- Fetch table names (T1 and T2)
- Dump table T1
- Rename table T2 to T3 generates RENAME event
- Dump table T2 is noop as table doesn’t exist.
- In target after load, it only have T1.
- Apply RENAME event will fail as T2 doesn’t exist in target.

This feature can be supported in next phase development as it need proper design to keep track
of renamed tables/partitions. 
So, for time being, we shall disable rename operations when bootstrap dump in progress to
avoid any inconsistent state.

  was:
Currently, bootstrap dump shall lead to data loss when any rename happens while dump in progress.
This feature can be supported in next phase development as it need proper design to keep track
of renamed tables/partitions. 
So, for time being, we shall disable rename operations when bootstrap dump in progress to
avoid any inconsistent state.


> Disable rename operations during bootstrap dump
> -----------------------------------------------
>
>                 Key: HIVE-17183
>                 URL: https://issues.apache.org/jira/browse/HIVE-17183
>             Project: Hive
>          Issue Type: Sub-task
>          Components: repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>             Fix For: 3.0.0
>
>         Attachments: HIVE-17183.01.patch, HIVE-17183.02.patch, HIVE-17183.03.patch
>
>
> Currently, bootstrap dump shall lead to data loss when any rename happens while dump
in progress. 
> *Scenario:*
> - Fetch table names (T1 and T2)
> - Dump table T1
> - Rename table T2 to T3 generates RENAME event
> - Dump table T2 is noop as table doesn’t exist.
> - In target after load, it only have T1.
> - Apply RENAME event will fail as T2 doesn’t exist in target.
> This feature can be supported in next phase development as it need proper design to keep
track of renamed tables/partitions. 
> So, for time being, we shall disable rename operations when bootstrap dump in progress
to avoid any inconsistent state.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message