From issues-return-116794-archive-asf-public=cust-asf.ponee.io@hive.apache.org Mon May 7 10:34:10 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D7A29180648 for ; Mon, 7 May 2018 10:34:09 +0200 (CEST) Received: (qmail 60203 invoked by uid 500); 7 May 2018 08:34:08 -0000 Mailing-List: contact issues-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list issues@hive.apache.org Received: (qmail 60194 invoked by uid 99); 7 May 2018 08:34:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 May 2018 08:34:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 97736CA5C6 for ; Mon, 7 May 2018 08:34:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id uuoRBfvaWyyF for ; Mon, 7 May 2018 08:34:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 0B35F5F24C for ; Mon, 7 May 2018 08:34:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 50CE7E00DF for ; Mon, 7 May 2018 08:34:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 178D72129B for ; Mon, 7 May 2018 08:34:00 +0000 (UTC) Date: Mon, 7 May 2018 08:34:00 +0000 (UTC) From: "Sankar Hariappan (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [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. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-19435?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-19435: ------------------------------------ Description:=20 If the incremental dump have=C2=A0drop of partitioned table followed by cre= ate/insert on non-partitioned table with same name, doesn't replicate the d= ata. Explained below. Let's say we have a partitioned table T1 which was already replicated to ta= rget. DROP_TABLE(T1)->CREATE_TABLE(T1) (Non-partitioned) -> INSERT(T1)(10)=C2=A0 After REPL LOAD, T1 doesn't have any data. Same is valid for no-partitioned to partitioned case as well. =C2=A0 was: If the incremental dump have=C2=A0drop of partitioned table followed by cre= ate/insert on non-partitioned table with same name, doesn't replicate the d= ata. Explained below. Let's say we have a partitioned table T1 which was already replicated to ta= rget. DROP_TABLE(T1)->CREATE_TABLE(T1) (Non-partitioned) -> INSERT(T1)(10)=C2=A0 After REPL LOAD, T1 doesn't have any data. =C2=A0 > Incremental replication cause data loss if table with same name is droppe= d 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=C2=A0drop of partitioned table followed by c= reate/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)=C2= =A0 > After REPL LOAD, T1 doesn't have any data. > Same is valid for no-partitioned to partitioned case as well. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)