You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/12/08 09:00:04 UTC

[jira] [Work logged] (HIVE-25781) Restore multi-threaded support in Cleaner after HIVE-25115

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

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

                Author: ASF GitHub Bot
            Created on: 08/Dec/21 09:00
            Start Date: 08/Dec/21 09:00
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ merged pull request #2825:
URL: https://github.com/apache/hive/pull/2825


   


-- 
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.

To unsubscribe, e-mail: gitbox-unsubscribe@hive.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

            Worklog Id:     (was: 692326)
    Remaining Estimate: 0h
            Time Spent: 10m

> Restore multi-threaded support in Cleaner after HIVE-25115
> ----------------------------------------------------------
>
>                 Key: HIVE-25781
>                 URL: https://issues.apache.org/jira/browse/HIVE-25781
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Denys Kuzmenko
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the case of accumulated entries for the same table/partition, they should be processed one by one in ASC order of write_id's.
> However, to support multi-threaded processing in the Cleaner, we need to make sure that the entries from the same group are not processed concurrently by multiple threads. 
> One of the solutions that don't involve synchronization (check if already in flight, re-try when possible) would be to move the entries from the same group to the next Cleaner cycle.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)