You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Sankar Hariappan (JIRA)" <ji...@apache.org> on 2018/04/16 06:09:00 UTC

[jira] [Assigned] (HIVE-19219) Hive replicated database is out of sync if events are cleaned-up.

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

Sankar Hariappan reassigned HIVE-19219:
---------------------------------------


> 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: Sub-task
>    Affects Versions: 3.0.0
>            Reporter: Sankar Hariappan
>            Assignee: Sankar Hariappan
>            Priority: Major
>              Labels: DR, 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 last completed event (passed as the fromEventId argument), is still present in source notification_log table. If it is not present, it should error out saying that events are missing.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)