[
https://issues.apache.org/jira/browse/HIVE-19219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-19219:
----------------------------------
Labels: DR pull-request-available replication (was: DR replication)
> 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)
