[
https://issues.apache.org/jira/browse/HIVE-24909?focusedWorklogId=575339&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-575339
]
ASF GitHub Bot logged work on HIVE-24909:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Apr/21 06:33
Start Date: 01/Apr/21 06:33
Worklog Time Spent: 10m
Work Description: hmangla98 commented on a change in pull request #2101:
URL: https://github.com/apache/hive/pull/2101#discussion_r605407659
##########
File path: ql/src/java/org/apache/hadoop/hive/ql/lockmgr/DbTxnManager.java
##########
@@ -227,6 +228,12 @@ public long openTxn(Context ctx, String user, TxnType
txnType) throws LockExcept
return openTxn(ctx, user, txnType, 0);
}
+ @Override
+ public long openTxn(Context ctx, String user, TxnType txnType, String
dbUnderReplication) throws LockException {
Review comment:
repl(Open/Rollback/Commit)Txn is specifically for replayed transaction.
So, by convention it would be REPL_CREATED transactions. It would be confusion
if we start introducing txnType in that.
--
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 575339)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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)
