Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 28 Jul 2015 20:24:04 +0000 (UTC)
From: "Xiaoyu Yao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12849719.1438113191000.311636.1438115044783@Atlassian.JIRA>
In-Reply-To: <JIRA.12849719.1438113191000@Atlassian.JIRA>
References: <JIRA.12849719.1438113191000@Atlassian.JIRA>
 <JIRA.12849719.1438113191808@arcas>
Subject: [jira] [Updated] (HDFS-8830) Support add/remove directories to an
 existing encryption zone
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Xiaoyu Yao updated HDFS-8830:
-----------------------------
    Attachment:     (was: HDFS-8830.01.patch)

> Support add/remove directories to an existing encryption zone
> -------------------------------------------------------------
>
>                 Key: HDFS-8830
>                 URL: https://issues.apache.org/jira/browse/HDFS-8830
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>         Attachments: HDFS-8830.01.patch
>
>
> This is the first step toward better "Scratch space" and "Soft Delete" support. We remove the assumption that the hdfs directory and encryption zone is 1 to 1 mapped and can't be changed once created.
> The encryption zone creation part is kept As-Is from Hadoop 2.4. We generalize the encryption zone and its directories from 1:1 to 1:many. This way, other directories such as scratch can be added to/removed from encryption zone as needed. Later on, files in these directories can be renamed within the same encryption zone efficiently. 


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