[
https://issues.apache.org/jira/browse/HIVE-26174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HIVE-26174:
----------------------------------
Labels: pull-request-available (was: )
> ALTER TABLE RENAME TO should check new db location
> --------------------------------------------------
>
> Key: HIVE-26174
> URL: https://issues.apache.org/jira/browse/HIVE-26174
> Project: Hive
> Issue Type: Improvement
> Reporter: Adrian Wang
> Assignee: Adrian Wang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, if we run
> ALTER TABLE db1.table1 RENAME TO db2.table2;
> and with `db1` and `db2` on different filesystem, for example `db1` as
> `"hdfs:/user/hive/warehouse/db1.db"`, and `db2` as
> `"s3://bucket/s3warehouse/db2.db"`, the new `db2.table2` will be under
> location `hdfs:/s3warehouse/db2.db/table2`, which looks quite strange.
> The idea is to ban this kind of operation, as we seem to intend to ban that,
> but the check was done after we changed file system scheme so it was always
> true.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
