hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Wilfong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3134) Drop table/index/database can result in orphaned locations
Date Thu, 14 Jun 2012 17:46:42 GMT

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

Kevin Wilfong commented on HIVE-3134:
-------------------------------------

Responded to comments on phabricator.
                
> Drop table/index/database can result in orphaned locations
> ----------------------------------------------------------
>
>                 Key: HIVE-3134
>                 URL: https://issues.apache.org/jira/browse/HIVE-3134
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>            Reporter: Kevin Wilfong
>            Assignee: Kevin Wilfong
>         Attachments: HIVE-3134.1.patch.txt
>
>
> Today when a managed table has a partition with a location which is not a subdirectory
of the table's location, when the table is dropped the partition's data is not deleted from
HDFS, resulting in an orphaned directory (the data exists but nothing points to it).
> The same applies to dropping a database with cascade and a table has a location outside
the database.
> I think it is safe to assume managed tables/partitions own the directories they point
to, so we should clean these up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message