You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/11/18 05:48:00 UTC

[jira] [Updated] (HIVE-26598) Fix unsetting of db params for optimized bootstrap when repl dump initiates data copy

     [ https://issues.apache.org/jira/browse/HIVE-26598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HIVE-26598:
----------------------------------
    Labels: pull-request-available  (was: )

> Fix unsetting of db params for optimized bootstrap when repl dump initiates data copy
> -------------------------------------------------------------------------------------
>
>                 Key: HIVE-26598
>                 URL: https://issues.apache.org/jira/browse/HIVE-26598
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Teddy Choi
>            Assignee: Rakshith C
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> when hive.repl.run.data.copy.tasks.on.target is set to false, repl dump task will initiate the copy task from source cluster to staging directory.
> In current code flow repl dump task dumps the metadata and then creates another repl dump task with datacopyIterators initialized.
> when the second dump cycle executes, it directly begins data copy tasks. Because of this we don't enter second reverse dump flow and  unsetDbPropertiesForOptimisedBootstrap is never set to true again.
> this results in db params (repl.target.for, repl.background.threads, etc) not being unset.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)