[
https://issues.apache.org/jira/browse/HIVE-26598?focusedWorklogId=839784&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-839784
]
ASF GitHub Bot logged work on HIVE-26598:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/23 00:21
Start Date: 18/Jan/23 00:21
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #3780:
URL: https://github.com/apache/hive/pull/3780#issuecomment-1386276643
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the [email protected] list if the patch is in
need of reviews.
Issue Time Tracking
-------------------
Worklog Id: (was: 839784)
Time Spent: 0.5h (was: 20m)
> 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: 0.5h
> 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)
