You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Peter Vary (Jira)" <ji...@apache.org> on 2022/03/04 13:39:00 UTC

[jira] [Resolved] (HIVE-25894) Table migration to Iceberg doesn't remove HMS partitions

     [ https://issues.apache.org/jira/browse/HIVE-25894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Vary resolved HIVE-25894.
-------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

Pushed to master.

Thanks for reporting [~boroknagyz] and for the review [~Marton Bod] and [~lpinter]!

> Table migration to Iceberg doesn't remove HMS partitions
> --------------------------------------------------------
>
>                 Key: HIVE-25894
>                 URL: https://issues.apache.org/jira/browse/HIVE-25894
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Zoltán Borók-Nagy
>            Assignee: Peter Vary
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Repro:
> {code:java}
> create table ice_part_migrate (i int) partitioned by (p int) stored as parquet;
> insert into ice_part_migrate partition(p=1) values (1), (11), (111);
> insert into ice_part_migrate partition(p=2) values (2), (22), (222);
> ALTER TABLE ice_part_migrate  SET TBLPROPERTIES ('storage_handler'='org.apache.iceberg.mr.hive.HiveIcebergStorageHandler');
> {code}
> Then looking at the HMS database:
> {code:java}
> => select "PART_NAME" from "PARTITIONS" p, "TBLS" t where t."TBL_ID"=p."TBL_ID" and t."TBL_NAME"='ice_part_migrate';
>  PART_NAME
> -----------
>  p=1
>  p=2
> {code}
> This is weird because Iceberg tables are supposed to be unpartitioned. It also breaks some precondition checks in Impala. Is there a particular reason to keep the partitions in HMS?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)