[HIVE-21286] Hive should support clean-up of previously bootstrapped tables when retry from different dump.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.0
• Fix Version/s: 4.0.0-alpha-1
• Component/s: repl
• Labels: DR Replication pull-request-available
• Target Version/s: 4.0.0
• Assignee: Sankar Hariappan
• Reporter: Sankar Hariappan
• Created: 19/Feb/19 09:17
• Updated: 17/Nov/22 08:55
• Resolved: 09/Mar/19 05:47

Description

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.clean.tables.from.bootstrap=<previous_bootstrap_dump_dir>

Hive will use this config only if the current dump is 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".

Issue Links

• is related to: HIVE-21029 External table replication for existing deployments running incremental replication.
• links to: GitHub Pull Request #551