Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 6 Jun 2017 04:41:18 +0000 (UTC)
From: "Sankar Hariappan (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.13075754.1496129241000.879.1496724078189@Atlassian.JIRA>
In-Reply-To: <JIRA.13075754.1496129241000@Atlassian.JIRA>
References: <JIRA.13075754.1496129241000@Atlassian.JIRA> <JIRA.13075754.1496129241404@jira-lw-us.apache.org>
Subject: [jira] [Work started] (HIVE-16785) Ensure replication actions are
 idempotent if any series of events are applied again.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 06 Jun 2017 04:41:22 -0000


     [ https://issues.apache.org/jira/browse/HIVE-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HIVE-16785 started by Sankar Hariappan.
-----------------------------------------------
> Ensure replication actions are idempotent if any series of events are applied again.
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-16785
>                 URL: https://issues.apache.org/jira/browse/HIVE-16785
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Hive, repl
>    Affects Versions: 2.1.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>              Labels: DR, replication
>
> Some of the events(ALTER, RENAME, TRUNCATE) are not idempotent and hence leads to failure of REPL LOAD if applied twice or applied on an object which is latest than current event. For example, if TRUNCATE is applied on a table which is already dropped will fail instead of noop.
> Also, need to consider the scenario where the object is missing while applying an event. For example, if RENAME_TABLE event is applied on target where the old table is missing should validate if table should be recreated or should treat the event as noop. This can be done by verifying the DB level last repl ID against the current event ID.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)