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 2019/12/07 17:08:00 UTC
[jira] [Assigned] (HIVE-22122) TxnHandler.getValidWriteIdsForTable
optimization for compacted tables
[ https://issues.apache.org/jira/browse/HIVE-22122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denys Kuzmenko reassigned HIVE-22122:
-------------------------------------
Assignee: Denys Kuzmenko
> TxnHandler.getValidWriteIdsForTable optimization for compacted tables
> ---------------------------------------------------------------------
>
> Key: HIVE-22122
> URL: https://issues.apache.org/jira/browse/HIVE-22122
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Reporter: Peter Vary
> Assignee: Denys Kuzmenko
> Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When we do not find open writes for the given validTxnList then we either:
> # do not have any writes on the table - we can return writeIdHwm = 0, and no invalid/aborted writes;
> # we have only compacted writes on the table - we can return writeIdHwm = nextWriteId -1, and no invalid/aborted;
> # we have compacted writes and some invalid writes on the table - we can return the lowest invalid write as a writeIdHwm and set it as invalid.
> What the current code does instead is sending writeIdHwm = nextWriteId -1, and sending every write as invalid. This results the same response in case 1-2, but probably a longer list in case 3.
> So we have place for some optimizations
--
This message was sent by Atlassian Jira
(v8.3.4#803005)