[
https://issues.apache.org/jira/browse/HIVE-21286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sankar Hariappan updated HIVE-21286:
------------------------------------
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.cleanup.bootstrap=<previous_bootstrap_dump_dir>
Hive will use this config only if the current dump is bootstrap dump or
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".
was:
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.cleanup.bootstrap=<previous_bootstrap_dump_dir>
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".
> Hive should support clean-up of incrementally 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
>
> 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.cleanup.bootstrap=<previous_bootstrap_dump_dir>
> Hive will use this config only if the current dump is bootstrap dump or
> 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)
