[jira] Commented: (HIVE-1116) alter table rename should rename hdfs location of table as well

["Prasad Chakka (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805985#action_12805985 ] 

Prasad Chakka commented on HIVE-1116:
-------------------------------------

I remember doing this quite sometime ago(only for non-external tables). Are you sure it doesn't work in any scenario?

> alter table rename should rename hdfs location of table as well
> ---------------------------------------------------------------
>
>                 Key: HIVE-1116
>                 URL: https://issues.apache.org/jira/browse/HIVE-1116
>             Project: Hadoop Hive
>          Issue Type: Bug
>            Reporter: Joydeep Sen Sarma
>
> if the location is not an external location - this would be safer.
> the problem right now is that it's tricky to use the drop and rename way of writing new data into a table. consider:
> Initialization block:
> drop table a_tmp
> create table a_tmp like a;
> Loading block:
> load data <newdata> into a_tmp;
> drop table a;
> alter table a_tmp rename to a;
> this looks safe. but it's not. if one runs this multiple times - then data is lost (since 'a' is pointing to 'a_tmp''s location after any iteration. and dropping table 'a' blows away loaded data in the next iteration). 
> if the location is being managed by Hive - then 'rename' should switch location as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.