[ https://issues.apache.org/jira/browse/HIVE-16706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021474#comment-16021474 ]
ASF GitHub Bot commented on HIVE-16706: --------------------------------------- GitHub user sankarh opened a pull request: https://github.com/apache/hive/pull/187 HIVE-16706: Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when dump in progress. You can merge this pull request into a Git repository by running: $ git pull https://github.com/sankarh/hive HIVE-16706 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/hive/pull/187.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 #187 ---- commit 7e9ed26ef2bd5a89cfe6df0ad22552dad003c82b Author: Sankar Hariappan <mailtosank...@gmail.com> Date: 2017-05-23T16:13:04Z HIVE-16706: Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when dump in progress. ---- > Bootstrap REPL DUMP shouldn't fail when a partition is dropped/renamed when > dump in progress. > --------------------------------------------------------------------------------------------- > > 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)