[HIVE-19435] Incremental replication cause data loss if a table is dropped followed by create and insert-into with different partition type.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0, 3.0.0
• Component/s: HiveServer2, repl
• Labels: DR pull-request-available replication
• Target Version/s: 3.0.0
• Assignee: Sankar Hariappan
• Reporter: Sankar Hariappan
• Created: 07/May/18 06:08
• Updated: 22/May/18 23:13
• Resolved: 13/May/18 07:34

Description

If the incremental dump have drop of partitioned table followed by create/insert on non-partitioned table with same name, doesn't replicate the data. Explained below.

Let's say we have a partitioned table T1 which was already replicated to target.

DROP_TABLE(T1)->CREATE_TABLE(T1) (Non-partitioned) -> INSERT(T1)(10) 

After REPL LOAD, T1 doesn't have any data.

Same is valid for non-partitioned to partitioned and partition spec mismatch case as well.

 

Issue Links

• links to: GitHub Pull Request #343