[
https://issues.apache.org/jira/browse/HIVE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731815#action_12731815
]
Prasad Chakka commented on HIVE-592:
------------------------------------
this patch changes the way 'alter table old_tbl_name rename to new_tbl_name'
behaves which is quite different from before and may affect users that depend
on older functionality.
older behavior:
just the table name is changed but the underlying hdfs location
(<warehouse_root>/old_tbl) is unchanged.
new behavior:
following changed on a rename for tables that are not created as external tables
- table name
- move underlying data from <warehouse_root>/old_tbl to <warehouse_root>/new_tbl
- location of table in metadata
- location of partitions in metadata
rename fails in the following scenarios
- a table with a new name already exists
- <warehouse_root>/new_tbl already exists or can't be created
- <warehouse_root>/old_tbl is not accessible
> renaming internal table should rename HDFS and also change path of the table
> and partitions accordingly.
> --------------------------------------------------------------------------------------------------------
>
> Key: HIVE-592
> URL: https://issues.apache.org/jira/browse/HIVE-592
> Project: Hadoop Hive
> Issue Type: Bug
> Affects Versions: 0.2.0, 0.3.0, 0.3.1, 0.4.0
> Reporter: Prasad Chakka
> Assignee: Prasad Chakka
> Fix For: 0.4.0
>
> Attachments: hive-592.2.patch, hive-592.3.patch
>
>
> rename table changes just the name of the table in metastore but not hdfs. so
> if a table with old name is created, it uses the hdfs directory pointing to
> the renamed table.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
