[
https://issues.apache.org/jira/browse/HIVE-28167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842311#comment-17842311
]
Sourabh Badhya commented on HIVE-28167:
---------------------------------------
[~zabetak] , Issuing a truncate command is far more efficient than performing a
full-table delete operation which would just create more files. Hence we would
like this to be the default behaviour. The config is deprecated since it was
already released in 4.0.0. We would like to deprecate it first and then
completely remove it in the next release.
> Full table deletion fails when converting to truncate for Iceberg and ACID
> tables
> ---------------------------------------------------------------------------------
>
> Key: HIVE-28167
> URL: https://issues.apache.org/jira/browse/HIVE-28167
> Project: Hive
> Issue Type: Bug
> Reporter: Sourabh Badhya
> Assignee: Sourabh Badhya
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.1.0
>
>
> A simple repro -
> {code:java}
> create table ice01 (id int, key int) stored by iceberg stored as orc
> tblproperties ('format-version'='2', 'write.delete.mode'='copy-on-write');
> insert into ice01 values (1,1),(2,1),(3,1),(4,1);
> insert into ice01 values (1,2),(2,2),(3,2),(4,2);
> insert into ice01 values (1,3),(2,3),(3,3),(4,3);
> insert into ice01 values (1,4),(2,4),(3,4),(4,4);
> insert into ice01 values (1,5),(2,5),(3,5),(4,5);
> explain analyze delete from ice01;
> delete from ice01;
> select count(*) from ice01;
> select * from ice01;
> describe formatted ice01; {code}
> The solution is to convert full table deletion to a truncate operation on the
> table.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
