[
https://issues.apache.org/jira/browse/HIVE-26409?focusedWorklogId=792706&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-792706
]
ASF GitHub Bot logged work on HIVE-26409:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jul/22 13:53
Start Date: 19/Jul/22 13:53
Worklog Time Spent: 10m
Work Description: SourabhBadhya commented on PR #3454:
URL: https://github.com/apache/hive/pull/3454#issuecomment-1189083211
@kgyrtkirk Could you please specify why there is a specific need for
__GLOBAL_LOCKS (global lock) for scheduled queries?
Issue Time Tracking
-------------------
Worklog Id: (was: 792706)
Time Spent: 20m (was: 10m)
> Assign a unique writeId for table in global locks for scheduled queries
> -----------------------------------------------------------------------
>
> Key: HIVE-26409
> URL: https://issues.apache.org/jira/browse/HIVE-26409
> Project: Hive
> Issue Type: Bug
> Reporter: Sourabh Badhya
> Assignee: Sourabh Badhya
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A unique writeId has to be assigned for the table in global locks because
> this will help in cleanup of records in COMPLETED_TXN_COMPONENTS table.
> Currently the writeId is NULL for this table. There was a situation which
> lead to large number of records in COMPLETED_TXN_COMPONENTS table because
> these records had writeId as NULL and this subsequently lead to OOM errors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
