[jira] [Work stopped] (HIVE-19219) Incremental REPL DUMP should throw error if requested events are cleaned-up.

2018-04-16 Thread Sankar Hariappan (JIRA)

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

Work on HIVE-19219 stopped by Sankar Hariappan.
---
> Incremental REPL DUMP should throw error if requested 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
>
> Attachments: HIVE-19219.01.patch
>
>
> 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)


[jira] [Work stopped] (HIVE-19219) Incremental REPL DUMP should throw error if requested events are cleaned-up.

2018-04-16 Thread Sankar Hariappan (JIRA)

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

Work on HIVE-19219 stopped by Sankar Hariappan.
---
> Incremental REPL DUMP should throw error if requested 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
>
> Attachments: HIVE-19219.01.patch
>
>
> 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)