[jira] [Work logged] (HIVE-26174) disable rename table across dbs when on different filesystem

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

                Author: ASF GitHub Bot
            Created on: 10/May/22 02:48
            Start Date: 10/May/22 02:48
    Worklog Time Spent: 10m 
      Work Description: adrian-wang commented on PR #3240:
URL: https://github.com/apache/hive/pull/3240#issuecomment-1121829345

   Hi @ayushtkn , In our customers' scenario, they want to put table data in HDFS, while some stale tables will be archived to cloud store. They were using this command and thought that data should be placed in cloud store, but after a while they found it is still in HDFS. Besides, currently if we have two dbs located on two different HDFS services, the command would fail, Hence I think we should not allow rename when two dbs are on different storages.




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

    Worklog Id:     (was: 768291)
    Time Spent: 20m  (was: 10m)

> disable rename table across dbs when on different filesystem
> ------------------------------------------------------------
>
>                 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: 20m
>  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)