[
https://issues.apache.org/jira/browse/HIVE-26942?focusedWorklogId=839502&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-839502
]
ASF GitHub Bot logged work on HIVE-26942:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Jan/23 03:58
Start Date: 17/Jan/23 03:58
Worklog Time Spent: 10m
Work Description: shreenidhiSaigaonkar commented on PR #3951:
URL: https://github.com/apache/hive/pull/3951#issuecomment-1384801756
@pudidic need review on this
Issue Time Tracking
-------------------
Worklog Id: (was: 839502)
Time Spent: 0.5h (was: 20m)
> Prevent updation of "repl.target.last.id" when RESUME action initiated
> ----------------------------------------------------------------------
>
> Key: HIVE-26942
> URL: https://issues.apache.org/jira/browse/HIVE-26942
> Project: Hive
> Issue Type: Task
> Reporter: Shreenidhi
> Assignee: Shreenidhi
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> *Problem :*
> Currently when "repl.last.id" get's changed/updated this updates the
> corresponding "repl.target.last.id" too. This is problematic incase of resume
> because we are updating both the properties at source.
>
> *Solution :*
> To prevent the updation of "repl.target.last.id" whenever "repl.last.id"
> changed, we can introduce new db param called "repl.resume.started". This new
> param will be set to "true" by orchestrator when RESUME is initiated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
