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

Posted to issues@hive.apache.org by "Teddy Choi (Jira)" <ji...@apache.org> on 2022/10/12 02:19:00 UTC

[jira] [Commented] (HIVE-26598) Fix unset db params for optimized bootstrap incase of data copy tasks run on target and testcases

    [ https://issues.apache.org/jira/browse/HIVE-26598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616130#comment-17616130 ] 

Teddy Choi commented on HIVE-26598:
-----------------------------------

Hello [~rakshithc] , please update the status and create a corresponding PR. Thank you.

> Fix unset db params for optimized bootstrap incase of data copy tasks run on target and testcases
> -------------------------------------------------------------------------------------------------
>
>                 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
>
> 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)