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 2023/01/16 06:58:00 UTC
[jira] [Updated] (HIVE-26942) Prevent updation of "repl.target.last.id" when RESUME action initiated
[ https://issues.apache.org/jira/browse/HIVE-26942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HIVE-26942:
----------------------------------
Labels: pull-request-available (was: )
> 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: 10m
> 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)