You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/05/07 08:43:00 UTC
[jira] [Commented] (HIVE-19435) Incremental replication cause data
loss if a table 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:comment-tabpanel&focusedCommentId=16465635#comment-16465635 ]
ASF GitHub Bot commented on HIVE-19435:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/343
HIVE-19435: Incremental replication cause data loss if a table is dropped followed by create and insert-into with different partition type.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-19435
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/343.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #343
----
commit 5d1d9dccbd8298ee8b593283315a6ad4f0f33c6e
Author: Sankar Hariappan <ma...@...>
Date: 2018-05-07T08:41:05Z
HIVE-19435: Incremental replication cause data loss if a table is dropped followed by create and insert-into with different partition type.
----
> 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
>
>
> 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 no-partitioned to partitioned case as well.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)