From issues-return-160818-archive-asf-public=cust-asf.ponee.io@hive.apache.org Thu Jun 20 02:29:03 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id A6BDE18060F for ; Thu, 20 Jun 2019 04:29:03 +0200 (CEST) Received: (qmail 96404 invoked by uid 500); 20 Jun 2019 02:29: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 96395 invoked by uid 99); 20 Jun 2019 02:29:03 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Jun 2019 02:29:03 +0000 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 C4BA6E2DE0 for ; Thu, 20 Jun 2019 02:29: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 E7DA62544E for ; Thu, 20 Jun 2019 02:29:00 +0000 (UTC) Date: Thu, 20 Jun 2019 02:29:00 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Work logged] (HIVE-21764) REPL DUMP should detect and bootstrap any rename table events where old table was excluded but renamed table is included. 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-21764?focusedWorklogId=3D= 263495&page=3Dcom.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpa= nel#worklog-263495 ] ASF GitHub Bot logged work on HIVE-21764: ----------------------------------------- Author: ASF GitHub Bot Created on: 20/Jun/19 02:28 Start Date: 20/Jun/19 02:28 Worklog Time Spent: 10m=20 Work Description: maheshk114 commented on pull request #679: HIVE-217= 64 : REPL DUMP should detect and bootstrap any rename table events where ol= d table was excluded but renamed table is included. URL: https://github.com/apache/hive/pull/679 =20 =20 =E2=80=A6 =20 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. =20 For queries about this service, please contact Infrastructure at: users@infra.apache.org Issue Time Tracking ------------------- Worklog Id: (was: 263495) Time Spent: 10m Remaining Estimate: 0h > REPL DUMP should detect and bootstrap any rename table events where old t= able was excluded but renamed table is included. > -------------------------------------------------------------------------= ------------------------------------------------ > > Key: HIVE-21764 > URL: https://issues.apache.org/jira/browse/HIVE-21764 > Project: Hive > Issue Type: Sub-task > Components: repl > Reporter: Sankar Hariappan > Assignee: mahesh kumar behera > Priority: Major > Labels: DR, Replication, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > REPL DUMP fetches the events from NOTIFICATION_LOG table based on regular= expression + inclusion/exclusion list. So, in case of rename table event, = the event will be ignored if old table doesn't match the pattern but the ne= w table should be bootstrapped. REPL DUMP should have a mechanism to detect= such tables and automatically bootstrap with incremental replication.Also,= if renamed table is excluded from replication policy, then need to drop th= e old table at target as well.=C2=A0 > There are 4 scenarios that needs to be handled. > # Both new name and old name satisfies the table name pattern filter. > ## No need to do anything. The incremental event for rename should take = care of the replication. > # Both the names does not satisfy the table name pattern filter. > ## Both the names are not in the scope of the policy and thus nothing ne= eds to be done. > # New name satisfies the pattern but the old name does not. > ## The table will not be present at the target. > ## Rename event handler for dump should detect this case and add the new= table name to the list of table for bootstrap. > ## All the events related to the table (new name) should be ignored. > ## If there is a drop event for the table (with new name), then remove t= he table from the list of tables to be bootstrapped. > ## In case of rename (double rename) > ### If the new name satisfies the table pattern, then add the new name t= o the list of tables to be bootstrapped and remove the old name from the li= st of tables to be bootstrapped. > ### If the new name does not satisfies then just removed the table name = from the list of tables to be bootstrapped. > # New name does not satisfies the pattern but the old name satisfies. > ## Change the rename event to a drop event. -- This message was sent by Atlassian JIRA (v7.6.3#76005)