[
https://issues.apache.org/jira/browse/HIVE-21286?focusedWorklogId=207652&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-207652
]
ASF GitHub Bot logged work on HIVE-21286:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Mar/19 06:43
Start Date: 05/Mar/19 06:43
Worklog Time Spent: 10m
Work Description: sankarh commented on pull request #551: HIVE-21286:
Hive should support clean-up of previously bootstrapped tables when retry from
different dump.
URL: https://github.com/apache/hive/pull/551#discussion_r262364809
##########
File path: ql/src/java/org/apache/hadoop/hive/ql/exec/repl/util/ReplUtils.java
##########
@@ -66,6 +66,10 @@
// tasks.
public static final String REPL_CURRENT_TBL_WRITE_ID =
"hive.repl.current.table.write.id";
+ // Configuration to be received via WITH clause of REPL LOAD to rollback any
previously failed
+ // bootstrap load.
+ public static final String REPL_ROLLBACK_BOOTSTRAP_LOAD_CONFIG =
"hive.repl.rollback.bootstrap.load";
Review comment:
Ok thanks! I like hive.repl.clean.tables.from.bootstrap. :)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 207652)
Time Spent: 3h 40m (was: 3.5h)
> Hive should support clean-up of previously bootstrapped tables when retry
> from different dump.
> ----------------------------------------------------------------------------------------------
>
> Key: HIVE-21286
> URL: https://issues.apache.org/jira/browse/HIVE-21286
> Project: Hive
> Issue Type: Bug
> Components: repl
> Affects Versions: 4.0.0
> Reporter: Sankar Hariappan
> Assignee: Sankar Hariappan
> Priority: Major
> Labels: DR, Replication, pull-request-available
> Attachments: HIVE-21286.01.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> If external tables are enabled for replication on an existing repl policy,
> then bootstrapping of external tables are combined with incremental dump.
> If incremental bootstrap load fails with non-retryable error for which user
> will have to manually drop all the external tables before trying with another
> bootstrap dump. For full bootstrap, to retry with different dump, we
> suggested user to drop the DB but in this case they need to manually drop all
> the external tables which is not so user friendly. So, need to handle it in
> Hive side as follows.
> REPL LOAD takes additional config (passed by user in WITH clause) that says,
> drop all the tables which are bootstrapped from previous dump.
> hive.repl.rollback.bootstrap.load=<previous_bootstrap_dump_dir>
> Hive will use this config only if the current dump is bootstrap dump or
> combined bootstrap in incremental dump.
> Caution to be taken by user that this config should not be passed if previous
> REPL LOAD (with bootstrap) was successful or any successful incremental
> dump+load happened after "previous_bootstrap_dump_dir".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
