hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Work logged] (HIVE-21286) Hive should support clean-up of previously bootstrapped tables when retry from different dump.
Date Tue, 05 Mar 2019 04:28:00 GMT


ASF GitHub Bot logged work on HIVE-21286:

                Author: ASF GitHub Bot
            Created on: 05/Mar/19 04:27
            Start Date: 05/Mar/19 04:27
    Worklog Time Spent: 10m 
      Work Description: ashutosh-bapat commented on pull request #551: HIVE-21286: Hive should
support clean-up of previously bootstrapped tables when retry from different dump.

 File path: ql/src/java/org/apache/hadoop/hive/ql/exec/repl/util/
 @@ -66,6 +66,10 @@
   // tasks.
   public static final String REPL_CURRENT_TBL_WRITE_ID = "";
+  // Configuration to be received via WITH clause of REPL LOAD to rollback any previously
+  // bootstrap load.
+  public static final String REPL_ROLLBACK_BOOTSTRAP_LOAD_CONFIG = "hive.repl.rollback.bootstrap.load";
 Review comment:
   In that case, I think we need a better name. The current name suggests that it can be used
for any bootstrap dump. I understand that this whole concept of incremental bootstrap is confusing.
But we should try to reduce the confusion for the user.
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:

Issue Time Tracking

    Worklog Id:     (was: 207598)
    Time Spent: 1h 50m  (was: 1h 40m)

> Hive should support clean-up of previously bootstrapped tables when retry from different
> ----------------------------------------------------------------------------------------------
>                 Key: HIVE-21286
>                 URL:
>             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: 1h 50m
>  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

View raw message