[ 
https://issues.apache.org/jira/browse/HIVE-21286?focusedWorklogId=208448&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-208448
 ]

ASF GitHub Bot logged work on HIVE-21286:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Mar/19 06:13
            Start Date: 06/Mar/19 06:13
    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.
URL: https://github.com/apache/hive/pull/551#discussion_r262801299
 
 

 ##########
 File path: ql/src/java/org/apache/hadoop/hive/ql/exec/repl/ReplLoadTask.java
 ##########
 @@ -298,25 +298,26 @@ a database ( directory )
    * @throws IOException File operations failure.
    * @throws InvalidInputException Invalid input dump directory.
    */
-  private void bootstrapRollbackTask() throws HiveException, IOException, 
InvalidInputException {
-    Path bootstrapDirectory = new PathBuilder(work.bootstrapDumpToRollback)
+  private void cleanTablesFromBootstrap() throws HiveException, IOException, 
InvalidInputException {
+    Path bootstrapDirectory = new PathBuilder(work.bootstrapDumpToCleanTables)
             .addDescendant(ReplUtils.INC_BOOTSTRAP_ROOT_DIR_NAME).build();
     FileSystem fs = bootstrapDirectory.getFileSystem(conf);
 
     if (!fs.exists(bootstrapDirectory)) {
-      throw new InvalidInputException("Input bootstrap dump directory to 
rollback doesn't exist: "
+      throw new InvalidInputException("Input bootstrap dump directory to clean 
tables is invalid: "
 
 Review comment:
   Grammar suggestion "Bootstrap dump directory specified to clean tables from 
is invalid"
 
----------------------------------------------------------------
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: 208448)
    Time Spent: 4h 50m  (was: 4h 40m)

> 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, HIVE-21286.02.patch
>
>          Time Spent: 4h 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.clean.tables.from.bootstrap=<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)

Reply via email to