[
https://issues.apache.org/jira/browse/HIVE-23107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17083948#comment-17083948
]
Peter Vary commented on HIVE-23107:
-----------------------------------
Finally a green run +1
> 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, HIVE-23107.04.patch, HIVE-23107.05.patch,
> HIVE-23107.06.patch, HIVE-23107.07.patch, HIVE-23107.08.patch,
> HIVE-23107.09.patch, HIVE-23107.10.patch, HIVE-23107.11.patch,
> HIVE-23107.12.patch, HIVE-23107.13.patch, HIVE-23107.14.patch,
> HIVE-23107.15.patch, HIVE-23107.16.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)
