[
https://issues.apache.org/jira/browse/HIVE-27360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangbutao updated HIVE-27360:
------------------------------
Description:
If you create a managed iceberg table without specifying the location and the
database has both location and managed_location, the final iceberg table
location will be on database location instead of managed_location. But you can
see a the database managed_location also has a iceberg table subdirectory which
is always here even if the table was dropped.
We should ensure the managed iceberg table always on database managed_location
in case of database managed_location existing. The direct and simple way is we
can use the created hms table location before committing iceberg table to avoid
creating a new iceberg location.
> Iceberg: Don't create a new iceberg location if hms table already has a
> default location
> -----------------------------------------------------------------------------------------
>
> Key: HIVE-27360
> URL: https://issues.apache.org/jira/browse/HIVE-27360
> Project: Hive
> Issue Type: Improvement
> Components: Iceberg integration
> Reporter: zhangbutao
> Assignee: zhangbutao
> Priority: Major
>
> If you create a managed iceberg table without specifying the location and the
> database has both location and managed_location, the final iceberg table
> location will be on database location instead of managed_location. But you
> can see a the database managed_location also has a iceberg table subdirectory
> which is always here even if the table was dropped.
> We should ensure the managed iceberg table always on database
> managed_location in case of database managed_location existing. The direct
> and simple way is we can use the created hms table location before
> committing iceberg table to avoid creating a new iceberg location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
