Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C512918212 for ; Sat, 30 Jan 2016 00:44:40 +0000 (UTC) Received: (qmail 7956 invoked by uid 500); 30 Jan 2016 00:44:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 7760 invoked by uid 500); 30 Jan 2016 00:44:40 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 7401 invoked by uid 99); 30 Jan 2016 00:44:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 30 Jan 2016 00:44:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 08AF12C0AFA for ; Sat, 30 Jan 2016 00:44:40 +0000 (UTC) Date: Sat, 30 Jan 2016 00:44:40 +0000 (UTC) From: "Zhe Zhang (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-9244) Support nested encryption zones MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhe Zhang updated HDFS-9244: ---------------------------- Attachment: HDFS-9244.02.patch Extending {{testEncryptionZoneWithTrash}} to verify behavior of nested EZs. Assume we have {{/topEZ/nestedEZ}}. The current Trash logic (in particular {{DistributedFileSystem#getTrashRoot}}), considers {{nestedEZ}} to be root dir of an EZ ({{ez.getPath().equals(absSrc)}}). Therefore when we remove {{nesteEZ}} it goes to {{/users/username/.Trash/topEZ/nestedEZ}}. As part of the rm, {{{{/users/username/.Trash/topEZ}} will be created. Later when we rm {{/topEZ}}, there will be a name clash and {{/users/username/.Trash/topEZxxxx}} will be created, {{xxxx}} is timestamp. So all deleted data is still in Trash, but additional recovery logic is needed. If we want to avoid this we should update {{DistributedFileSystem#getTrashRoot}} to check if the parent of the given path is in an EZ (or is an EZ itself). We can either add the logic in {{getTrashRoot}} or add an API in {{EncryptionZoneManager}}. Once we reach an agreement I'll update the patch. > Support nested encryption zones > ------------------------------- > > Key: HDFS-9244 > URL: https://issues.apache.org/jira/browse/HDFS-9244 > Project: Hadoop HDFS > Issue Type: New Feature > Components: encryption > Reporter: Xiaoyu Yao > Assignee: Zhe Zhang > Attachments: HDFS-9244.00.patch, HDFS-9244.01.patch, HDFS-9244.02.patch > > > This JIRA is opened to track adding support of nested encryption zone based on [~andrew.wang]'s [comment |https://issues.apache.org/jira/browse/HDFS-8747?focusedCommentId=14654141&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14654141] for certain use cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)