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

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

                Author: ASF GitHub Bot
            Created on: 19/Jan/23 05:16
            Start Date: 19/Jan/23 05:16
    Worklog Time Spent: 10m 
      Work Description: pudidic merged PR #3780:
URL: https://github.com/apache/hive/pull/3780




Issue Time Tracking
-------------------

    Worklog Id:     (was: 840150)
    Time Spent: 1h 10m  (was: 1h)

> 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: 1h 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)

Reply via email to