From issues-return-148178-archive-asf-public=cust-asf.ponee.io@hive.apache.org Thu Jan 31 04:48:05 2019 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 42A0E180652 for ; Thu, 31 Jan 2019 05:48:05 +0100 (CET) Received: (qmail 76122 invoked by uid 500); 31 Jan 2019 04:48:03 -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 76112 invoked by uid 99); 31 Jan 2019 04:48:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2019 04:48:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 422A4180A69 for ; Thu, 31 Jan 2019 04:48:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-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-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Y9PGnBpKrS78 for ; Thu, 31 Jan 2019 04:48:02 +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 C405D5F6BF for ; Thu, 31 Jan 2019 04:48:01 +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 46133E2697 for ; Thu, 31 Jan 2019 04:48:01 +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 7F744243BF for ; Thu, 31 Jan 2019 04:48:00 +0000 (UTC) Date: Thu, 31 Jan 2019 04:48:00 +0000 (UTC) From: "Sankar Hariappan (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HIVE-21029) External table replication for existing deployments running incremental replication. 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-21029?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] Sankar Hariappan updated HIVE-21029: ------------------------------------ Attachment: HIVE-21029.04.patch > External table replication for existing deployments running incremental r= eplication. > -------------------------------------------------------------------------= ----------- > > Key: HIVE-21029 > URL: https://issues.apache.org/jira/browse/HIVE-21029 > Project: Hive > Issue Type: Bug > Components: repl > Affects Versions: 3.0.0, 3.1.0, 3.1.1 > Reporter: anishek > Assignee: Sankar Hariappan > Priority: Critical > Labels: pull-request-available > Fix For: 4.0.0 > > Attachments: HIVE-21029.01.patch, HIVE-21029.02.patch, HIVE-21029= .03.patch, HIVE-21029.04.patch > > > Existing deployments using hive replication do not get external tables re= plicated. For such deployments to enable external table replication they wi= ll have to provide a specific switch to first bootstrap external tables as = part of hive incremental replication, following which the incremental repli= cation will take care of further changes in external tables. > The switch will be provided by an additional hive configuration (for ex: = hive.repl.bootstrap.external.tables) and is to be used in=20 > {code} WITH {code} clause of=20 > {code} REPL DUMP {code} command.=20 > Additionally the existing hive config _hive.repl.include.external.tables_= will always have to be set to "true" in the above clause.=20 > Proposed usage for enabling external tables replication on existing repli= cation policy. > 1. Consider an ongoing repl policy in incremental phase. > Enable hive.repl.include.external.tables=3Dtrue and hive.repl.bootstrap.e= xternal.tables=3Dtrue in next incremental REPL DUMP. > - Dumps all events but skips events related to external tables. > - Instead, combine bootstrap dump for all external tables under =E2=80=9C= _bootstrap=E2=80=9D directory. > - Also, includes the data locations file "_external_tables_info=E2=80=9D. > - LIMIT or TO clause shouldn=E2=80=99t be there to ensure the latest even= ts are dumped before bootstrap dumping external tables. > 2. REPL LOAD on this dump applies all the events first, copies external t= ables data and then bootstrap external tables (metadata). > - It is possible that the external tables (metadata) are not point-in tim= e consistent with rest of the tables. > - But, it would be eventually consistent when the next incremental load i= s applied. > - This REPL LOAD is fault tolerant and can be retried if failed. > 3. All future REPL DUMPs on this repl policy should set hive.repl.bootstr= ap.external.tables=3Dfalse. > - If not set to false, then target might end up having inconsistent set o= f external tables as bootstrap wouldn=E2=80=99t clean-up any dropped extern= al tables. -- This message was sent by Atlassian JIRA (v7.6.3#76005)