You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/03/21 09:02:00 UTC

[jira] [Work logged] (HIVE-27160) Iceberg: Optimise delete (entire) data from table

     [ https://issues.apache.org/jira/browse/HIVE-27160?focusedWorklogId=851961&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-851961 ]

ASF GitHub Bot logged work on HIVE-27160:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 21/Mar/23 09:01
            Start Date: 21/Mar/23 09:01
    Worklog Time Spent: 10m 
      Work Description: deniskuzZ merged PR #4109:
URL: https://github.com/apache/hive/pull/4109




Issue Time Tracking
-------------------

            Worklog Id:     (was: 851961)
    Remaining Estimate: 0h
            Time Spent: 10m

> Iceberg: Optimise delete (entire) data from table
> -------------------------------------------------
>
>                 Key: HIVE-27160
>                 URL: https://issues.apache.org/jira/browse/HIVE-27160
>             Project: Hive
>          Issue Type: Task
>            Reporter: Denys Kuzmenko
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, in MOR mode, Hive creates "positional delete" files during deletes. With "Delete from ", the entire dataset in the table or partition is written as a "positional delete" file.
> During the read operation, all these files are read again causing huge delay.
> Proposal: apply "truncate" optimization in case of "delete *".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)