[
https://issues.apache.org/jira/browse/HIVE-27020?focusedWorklogId=857255&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-857255
]
ASF GitHub Bot logged work on HIVE-27020:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/23 18:21
Start Date: 16/Apr/23 18:21
Worklog Time Spent: 10m
Work Description: SourabhBadhya commented on code in PR #4091:
URL: https://github.com/apache/hive/pull/4091#discussion_r1167991540
##########
standalone-metastore/metastore-server/src/main/java/org/apache/hadoop/hive/metastore/txn/TxnUtils.java:
##########
@@ -82,7 +82,29 @@ public static ValidTxnList
createValidTxnListForCleaner(GetOpenTxnsResponse txns
bitSet.set(0, abortedTxns.length);
//add ValidCleanerTxnList? - could be problematic for all the places that
read it from
// string as they'd have to know which object to instantiate
- return new ValidReadTxnList(abortedTxns, bitSet, highWaterMark,
Long.MAX_VALUE);
+ return new ValidReadTxnList(abortedTxns, bitSet, highWatermark,
Long.MAX_VALUE);
+ }
+
+ public static ValidTxnList
createValidTxnListForAbortedTxnCleaner(GetOpenTxnsResponse txns, long
minOpenTxn) {
Review Comment:
I have renamed `createValidTxnListForCleaner` to
`createValidTxnListForCompactionCleaner`. This is different from
`createValidTxnListForAbortedTxnCleaner`, mainly that we dont truncate the
abortedBits which seems unnecessary. We are also not concerned if there are
open txns from other tables present in this list (open txn on the same table
will obviously be handled since highWatermark will be updated to min open txn
for that table - 1). We just create an exception list based on the
highWatermark and use it for the creating the validWriteIdList.
Issue Time Tracking
-------------------
Worklog Id: (was: 857255)
Time Spent: 13h 20m (was: 13h 10m)
> Implement a separate handler to handle aborted transaction cleanup
> ------------------------------------------------------------------
>
> Key: HIVE-27020
> URL: https://issues.apache.org/jira/browse/HIVE-27020
> Project: Hive
> Issue Type: Sub-task
> Reporter: Sourabh Badhya
> Assignee: Sourabh Badhya
> Priority: Major
> Labels: pull-request-available
> Time Spent: 13h 20m
> Remaining Estimate: 0h
>
> As described in the parent task, once the cleaner is separated into different
> entities, implement a separate handler which can create requests for aborted
> transactions cleanup. This would move the aborted transaction cleanup
> exclusively to the cleaner.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
