[
https://issues.apache.org/jira/browse/HIVE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466307#comment-16466307
]
Vineet Garg commented on HIVE-19435:
------------------------------------
[~sankarh] Is this a blocker for 3.0 release or can it be deferred to 3.1?
> Incremental replication cause data loss if a table is dropped followed by
> create and insert-into with different partition type.
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-19435
> URL: https://issues.apache.org/jira/browse/HIVE-19435
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2, repl
> Affects Versions: 3.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: DR, pull-request-available, replication
> Fix For: 3.0.0, 3.1.0
>
> Attachments: HIVE-19435.01.patch, HIVE-19435.02.patch
>
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
