[jira] [Updated] (HIVE-16706) Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after fetching the partitions in a batch.

2017-05-23 Thread Sankar Hariappan (JIRA)

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

Sankar Hariappan updated HIVE-16706:

Description: 
Currently, bootstrap REPL DUMP gets the partitions in a batch and then iterate 
through it. If any partition is dropped/renamed during iteration, it may lead 
to failure/exception. In this case, the partition should be skipped from dump 
and also need to ensure no failure of REPL DUMP and the subsequent incremental 
dump should ensure the consistent state of the table.

This bug is related to HIVE-16684.

  was:
Currently, bootstrap REPL DUMP gets the partitions in a batch and then iterate 
through it. If any partition is dropped/renamed during iteration, it will lead 
to failure/exception. In this case, the partition should be skipped from dump 
and also need to ensure no failure of REPL DUMP and the subsequent incremental 
dump should ensure the consistent state of the table.

This bug is related to HIVE-16684.


> Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after 
> fetching the partitions in a batch.
> 
>
> Key: HIVE-16706
> URL: https://issues.apache.org/jira/browse/HIVE-16706
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive, repl
>Affects Versions: 2.1.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>  Labels: DR, replication
>
> Currently, bootstrap REPL DUMP gets the partitions in a batch and then 
> iterate through it. If any partition is dropped/renamed during iteration, it 
> may lead to failure/exception. In this case, the partition should be skipped 
> from dump and also need to ensure no failure of REPL DUMP and the subsequent 
> incremental dump should ensure the consistent state of the table.
> This bug is related to HIVE-16684.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (HIVE-16706) Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after fetching the partitions in a batch.

2017-05-18 Thread Sankar Hariappan (JIRA)

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

Sankar Hariappan updated HIVE-16706:

Description: 
Currently, bootstrap REPL DUMP gets the partitions in a batch and then iterate 
through it. If any partition is dropped/renamed during iteration, it will lead 
to failure/exception. In this case, the partition should be skipped from dump 
and also need to ensure no failure of REPL DUMP and the subsequent incremental 
dump should ensure the consistent state of the table.

This bug is related to HIVE-16684.

  was:Currently, bootstrap REPL DUMP gets the partitions in a batch and then 
iterate through it. If any partition is dropped/renamed during iteration, it 
will lead to failure/exception. In this case, the partition should be skipped 
from dump and also need to ensure no failure of REPL DUMP and the subsequent 
incremental dump should ensure the consistent state of the table.


> Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after 
> fetching the partitions in a batch.
> 
>
> Key: HIVE-16706
> URL: https://issues.apache.org/jira/browse/HIVE-16706
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive, repl
>Affects Versions: 2.1.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>  Labels: DR, replication
>
> Currently, bootstrap REPL DUMP gets the partitions in a batch and then 
> iterate through it. If any partition is dropped/renamed during iteration, it 
> will lead to failure/exception. In this case, the partition should be skipped 
> from dump and also need to ensure no failure of REPL DUMP and the subsequent 
> incremental dump should ensure the consistent state of the table.
> This bug is related to HIVE-16684.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (HIVE-16706) Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after fetching the partitions in a batch.

2017-05-18 Thread Sankar Hariappan (JIRA)

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

Sankar Hariappan updated HIVE-16706:

Labels: DR replication  (was: )

> Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed after 
> fetching the partitions in a batch.
> 
>
> Key: HIVE-16706
> URL: https://issues.apache.org/jira/browse/HIVE-16706
> Project: Hive
>  Issue Type: Sub-task
>  Components: Hive, repl
>Affects Versions: 2.1.0
>Reporter: Sankar Hariappan
>Assignee: Sankar Hariappan
>  Labels: DR, replication
>
> Currently, bootstrap REPL DUMP gets the partitions in a batch and then 
> iterate through it. If any partition is dropped/renamed during iteration, it 
> will lead to failure/exception. In this case, the partition should be skipped 
> from dump and also need to ensure no failure of REPL DUMP and the subsequent 
> incremental dump should ensure the consistent state of the table.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)