[
https://issues.apache.org/jira/browse/HIVE-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashutosh Chauhan updated HIVE-3702:
-----------------------------------
Fix Version/s: 0.11
> Renaming table changes table location scheme/authority
> ------------------------------------------------------
>
> Key: HIVE-3702
> URL: https://issues.apache.org/jira/browse/HIVE-3702
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.9.0
> Reporter: Kevin Wilfong
> Assignee: Kevin Wilfong
> Fix For: 0.11
>
> Attachments: HIVE-3702.1.patch.txt, HIVE-3702.2.patch.txt
>
>
> Renaming a table changes the location of the table to the default location of
> the database, followed by the table name. This means that if the default
> location of the database uses a different scheme/authority, an exception will
> get thrown attempting to move the data.
> Instead, the table's location should be made the default location of the
> database followed by the table name, but using the original location's scheme
> and authority.
> This only applies for managed tables, and there is already a check to ensure
> the new location doesn't already exist.
> This is analogous to what was done for partitions in HIVE-2875
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
