You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "László Pintér (Jira)" <ji...@apache.org> on 2020/04/02 10:33:00 UTC

[jira] [Updated] (HIVE-23107) Remove MIN_HISTORY_LEVEL table

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

László Pintér updated HIVE-23107:
---------------------------------
    Attachment: HIVE-23107.03.patch

> Remove MIN_HISTORY_LEVEL table
> ------------------------------
>
>                 Key: HIVE-23107
>                 URL: https://issues.apache.org/jira/browse/HIVE-23107
>             Project: Hive
>          Issue Type: Improvement
>          Components: Hive
>            Reporter: László Pintér
>            Assignee: László Pintér
>            Priority: Major
>         Attachments: HIVE-23107.01.patch, HIVE-23107.02.patch, HIVE-23107.03.patch
>
>
> MIN_HISTORY_LEVEL table is used in two places:
>  * Cleaner uses it to decide if the files can be removed - this could be replaced by adding a new column to compaction_queue storing the next_txn_id when the change was committed, and before cleaning checking the minimum open transaction id in the TXNS table
>  * Initiator uses it to decide if some items from TXN_TO_WRITE_ID table can be removed. This could be replaced by using the WRITE_SET.WS_COMMIT_ID.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)