[
https://issues.apache.org/jira/browse/HIVE-24909?focusedWorklogId=569801&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-569801
]
ASF GitHub Bot logged work on HIVE-24909:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Mar/21 15:40
Start Date: 22/Mar/21 15:40
Worklog Time Spent: 10m
Work Description: hmangla98 opened a new pull request #2101:
URL: https://github.com/apache/hive/pull/2101
What changes were proposed in this pull request?
Skip the repl events from getting logged in notification log
Why are the changes needed?
Currently REPL dump events are logged and replicated as a part of
replication policy. Whenever one replication cycle completed, we always have
one transaction left open on the target corresponding to repl dump operation.
This will never be caught up without manually dealing with the transaction on
target cluster.
Does this PR introduce any user-facing change?
No
How was this patch tested?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 569801)
Time Spent: 0.5h (was: 20m)
> Skip the repl events from getting logged in notification log
> ------------------------------------------------------------
>
> Key: HIVE-24909
> URL: https://issues.apache.org/jira/browse/HIVE-24909
> Project: Hive
> Issue Type: Bug
> Reporter: Haymant Mangla
> Assignee: Haymant Mangla
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently REPL dump events are logged and replicated as a part of replication
> policy. Whenever one replication cycle completed, we always have one
> transaction left open on the target corresponding to repl dump operation.
> This will never be caught up without manually dealing with the transaction on
> target cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
