You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/09 11:24:48 UTC

[jira] [Commented] (HIVE-3702) Renaming table changes table location scheme/authority

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

Hudson commented on HIVE-3702:
------------------------------

Integrated in Hive-trunk-hadoop2 #54 (See [https://builds.apache.org/job/Hive-trunk-hadoop2/54/])
    HIVE-3702 Renaming table changes table location scheme/authority
(Kevin Wilfong via namit) (Revision 1416875)

     Result = ABORTED
namit : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1416875
Files : 
* /hive/trunk/metastore/src/java/org/apache/hadoop/hive/metastore/HiveAlterHandler.java
* /hive/trunk/ql/src/test/org/apache/hadoop/hive/ql/hooks/VerifyOutputTableLocationSchemeIsFileHook.java
* /hive/trunk/ql/src/test/queries/clientpositive/rename_table_location.q
* /hive/trunk/ql/src/test/results/clientpositive/rename_table_location.q.out

                
> 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.0
>
>         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