You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2022/10/19 08:55:00 UTC

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

     [ https://issues.apache.org/jira/browse/HIVE-25781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Denys Kuzmenko updated HIVE-25781:
----------------------------------
    Fix Version/s: 4.0.0-alpha-1

> 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
>             Fix For: 4.0.0-alpha-1
>
>          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.10#820010)