[
https://issues.apache.org/jira/browse/HIVE-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439644#comment-16439644
]
ASF GitHub Bot commented on HIVE-19219:
---------------------------------------
GitHub user sankarh opened a pull request:
https://github.com/apache/hive/pull/334
HIVE-19219: Hive replicated database is out of sync if events are
cleaned-up.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sankarh/hive HIVE-19219
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/hive/pull/334.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 #334
----
commit b883f8b28c9f86e0cc731bc1b43c3706617bec81
Author: Sankar Hariappan <mailtosankarh@...>
Date: 2018-04-16T16:05:46Z
HIVE-19219: Hive replicated database is out of sync if events are
cleaned-up.
----
> Hive replicated database is out of sync if events are cleaned-up.
> -----------------------------------------------------------------
>
> Key: HIVE-19219
> URL: https://issues.apache.org/jira/browse/HIVE-19219
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: DR, pull-request-available, replication
> Fix For: 3.1.0
>
>
> This is the case where the events were deleted on source because of old event
> purging and hence min(source event id) > target event id (last replicated
> event id).
> Repl dump should fail in this case so that user can drop the database and
> bootstrap again.
> The next incremental repl dump could check if the events fetched from source
> notification_log table is retrieved in continuous sequence with no events
> missing. If any event is missing, it should throw error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
