[jira] [Work logged] (HIVE-26409) Assign a unique writeId for table in global locks for scheduled queries

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-26409?focusedWorklogId=792498&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-792498 ]

ASF GitHub Bot logged work on HIVE-26409:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 19/Jul/22 08:15
            Start Date: 19/Jul/22 08:15
    Worklog Time Spent: 10m 
      Work Description: SourabhBadhya opened a new pull request, #3454:
URL: https://github.com/apache/hive/pull/3454

   …eduled queries
   
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
   Assigning a unique writeId for table in global locks for scheduled queries.
   
   
   ### Why are the changes needed?
   Accumulation of records in the COMPLETED_TXN_COMPONENTS table due to these records not getting cleaned up in AcidHouseKeeperService.
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description, screenshot and/or a reproducable example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to the released Hive versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   No
   
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some test cases that check the changes thoroughly including negative and positive cases if possible.
   If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why it was difficult to add.
   -->
   Unit test




Issue Time Tracking
-------------------

            Worklog Id:     (was: 792498)
    Remaining Estimate: 0h
            Time Spent: 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
>          Time Spent: 10m
>  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)