[
https://issues.apache.org/jira/browse/HIVE-16990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088070#comment-16088070
]
ASF GitHub Bot commented on HIVE-16990:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/205
HIVE-16990: REPL LOAD should update last repl ID only after successful copy
of data files.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-16990
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/205.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 #205
----
commit 20bdd5dfeeec9366cb2a1e7a184758fbb1db1259
Author: Sankar Hariappan <mailtosank...@gmail.com>
Date: 2017-07-12T07:26:50Z
HIVE-16990: REPL LOAD should update last repl ID only after successful copy
of data files.
----
> REPL LOAD should update last repl ID only after successful copy of data files.
> ------------------------------------------------------------------------------
>
> Key: HIVE-16990
> URL: https://issues.apache.org/jira/browse/HIVE-16990
> Project: Hive
> Issue Type: Sub-task
> Components: Hive, repl
> Affects Versions: 2.1.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Labels: DR, replication
> Fix For: 3.0.0
>
> Attachments: HIVE-16990.01.patch
>
>
> For REPL LOAD operations that includes both metadata and data changes should
> follow the below rule.
> 1. Copy the metadata excluding the last repl ID.
> 2. Copy the data files
> 3. If Step 1 and 2 are successful, then update the last repl ID of the object.
> This rule will allow the the failed events to be re-applied by REPL LOAD and
> ensures no data loss due to failures.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
