[
https://issues.apache.org/jira/browse/HIVE-16785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047010#comment-16047010
]
ASF GitHub Bot commented on HIVE-16785:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/194
HIVE-16785: Ensure replication actions are idempotent if any series of
events are applied again.
Idempotent behaviour for all events during incremental load.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-16785
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/194.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #194
----
commit 741a824e253064854487983aaa9a8d31300384dc
Author: Sankar Hariappan <[email protected]>
Date: 2017-06-05T05:32:30Z
HIVE-16785: Ensure replication actions are idempotent if any series of
events are applied again.
----
> 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
> Attachments: HIVE-16785.01.patch
>
>
> 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.4.14#64029)
