You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2018/05/07 08:29:00 UTC
[jira] [Updated] (HIVE-19435) Incremental replication cause data
loss if table with same name is dropped followed by create and insert-into
with different partition type.
[ https://issues.apache.org/jira/browse/HIVE-19435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sankar Hariappan updated HIVE-19435:
------------------------------------
Summary: Incremental replication cause data loss if table with same name is dropped followed by create and insert-into with different partition type. (was: Data loss when incremental replication with drop partitioned table followed by create and insert-into non-partitioned table using same name.)
> Incremental replication cause data loss if table with same name 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, replication
> Fix For: 3.0.0, 3.1.0
>
>
> 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.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)