Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 13 Jun 2012 23:39:43 +0000 (UTC)
From: "Kevin Wilfong (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <1485911913.14022.1339630783343.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1412251579.14015.1339630665935.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HIVE-3134) Drop table/index/database can result
 in orphaned locations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-3134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Wilfong updated HIVE-3134:
--------------------------------

    Attachment: HIVE-3134.1.patch.txt
    
> 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
>            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