You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Chaoyu Tang (JIRA)" <ji...@apache.org> on 2016/09/07 12:53:21 UTC

[jira] [Updated] (HIVE-14626) Support Trash in Truncate Table

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

Chaoyu Tang updated HIVE-14626:
-------------------------------
    Attachment: HIVE-14626.1.patch

[~spena] I revised the patch. It cleans the directory contents only when it is encryption-zone protected. For other cases, we do trash/delete the directory followed by recreation as you suggested.
I have attached new patch here and also uploaded to RB for review. Thanks. 

> Support Trash in Truncate Table
> -------------------------------
>
>                 Key: HIVE-14626
>                 URL: https://issues.apache.org/jira/browse/HIVE-14626
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Query Processor
>            Reporter: Chaoyu Tang
>            Assignee: Chaoyu Tang
>            Priority: Minor
>         Attachments: HIVE-14626.1.patch, HIVE-14626.patch
>
>
> Currently Truncate Table (or Partition) is implemented using FileSystem.delete and then recreate the directory, so
> 1. it does not support HDFS Trash
> 2. if the table/partition directory is initially encryption protected, after being deleted and recreated, it is no more protected.
> The new implementation is to clean the contents of directory using multi-threaded trashFiles. If Trash is enabled and has a lower encryption level than the data directory, the files under it will be deleted. Otherwise, they will be Trashed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)