[
https://issues.apache.org/jira/browse/HIVE-26183?focusedWorklogId=765875&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-765875
]
ASF GitHub Bot logged work on HIVE-26183:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/May/22 08:50
Start Date: 04/May/22 08:50
Worklog Time Spent: 10m
Work Description: pvary merged PR #3251:
URL: https://github.com/apache/hive/pull/3251
Issue Time Tracking
-------------------
Worklog Id: (was: 765875)
Time Spent: 6h (was: 5h 50m)
> Create delete writer for the UPDATE statemens
> ---------------------------------------------
>
> Key: HIVE-26183
> URL: https://issues.apache.org/jira/browse/HIVE-26183
> Project: Hive
> Issue Type: Sub-task
> Reporter: Peter Vary
> Priority: Major
> Labels: pull-request-available
> Time Spent: 6h
> Remaining Estimate: 0h
>
> During the investigation of the updates of partitioned table we had the
> following issue:
> - Iceberg inserts are needed to be sorted by the new partition keys
> - Iceberg deletes are needed to be sorted by the old partition keys and
> filenames
> This could contradict each other. OTOH Hive updates create a single query and
> writes out the insert/delete record for ever row. This would mean plenty of
> open writers.
> We might want to create something like a
> https://github.com/apache/iceberg/blob/master/core/src/main/java/org/apache/iceberg/io/SortedPosDeleteWriter.java,
> but we do not want to keep the whole rows in memory.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
