Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 99C7D200C7E for ; Tue, 23 May 2017 18:13:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 98506160BD9; Tue, 23 May 2017 16:13:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 8E53C160BC3 for ; Tue, 23 May 2017 18:13:08 +0200 (CEST) Received: (qmail 39092 invoked by uid 500); 23 May 2017 16:13:07 -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 38899 invoked by uid 99); 23 May 2017 16:13:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 May 2017 16:13:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 4FA8CC0FD6 for ; Tue, 23 May 2017 16:13:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id XFQebDWYWx8x for ; Tue, 23 May 2017 16:13:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 5DD295FBC1 for ; Tue, 23 May 2017 16:13: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 D8851E0663 for ; Tue, 23 May 2017 16:13:05 +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 F059021B57 for ; Tue, 23 May 2017 16:13:04 +0000 (UTC) Date: Tue, 23 May 2017 16:13:04 +0000 (UTC) From: "Sankar Hariappan (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-16706) Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when dump in progress. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 23 May 2017 16:13:09 -0000 [ https://issues.apache.org/jira/browse/HIVE-16706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-16706: ------------------------------------ Summary: Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when dump in progress. (was: Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after fetching the partitions in a batch.) > Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when dump in progress. > --------------------------------------------------------------------------------------------- > > Key: HIVE-16706 > URL: https://issues.apache.org/jira/browse/HIVE-16706 > Project: Hive > Issue Type: Sub-task > Components: Hive, repl > Affects Versions: 2.1.0 > Reporter: Sankar Hariappan > Assignee: Sankar Hariappan > Labels: DR, replication > > Currently, bootstrap REPL DUMP gets the partitions in a batch and then iterate through it. If any partition is dropped/renamed during iteration, it may lead to failure/exception. In this case, the partition should be skipped from dump and also need to ensure no failure of REPL DUMP and the subsequent incremental dump should ensure the consistent state of the table. > This bug is related to HIVE-16684. -- This message was sent by Atlassian JIRA (v6.3.15#6346)