From hdfs-issues-return-207972-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jan 19 04:57:04 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 4125F180654 for ; Fri, 19 Jan 2018 04:57:04 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2D846160C49; Fri, 19 Jan 2018 03:57:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 72706160C26 for ; Fri, 19 Jan 2018 04:57:03 +0100 (CET) Received: (qmail 97583 invoked by uid 500); 19 Jan 2018 03:57:02 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 97569 invoked by uid 99); 19 Jan 2018 03:57:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jan 2018 03:57:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D792818086F for ; Fri, 19 Jan 2018 03:57:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.711 X-Spam-Level: X-Spam-Status: No, score=-108.711 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id K1ho49ttSe-9 for ; Fri, 19 Jan 2018 03:57:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DD0725F1F0 for ; Fri, 19 Jan 2018 03:57:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6E5D2E0959 for ; Fri, 19 Jan 2018 03:57:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 255FF21305 for ; Fri, 19 Jan 2018 03:57:00 +0000 (UTC) Date: Fri, 19 Jan 2018 03:57:00 +0000 (UTC) From: "chuanjie.duan (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-13037) Support protected path configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-13037?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:all-tabpanel ] chuanjie.duan updated HDFS-13037: --------------------------------- Description:=20 After Hadoop2.7 root path("/") cannot be deleted for any situration. But li= ke '/tmp','/user','/user/hive/warehouse' and so on, shouldn't be deleted mo= stly. So can we=C2=A0let user=C2=A0config=C2=A0 their own=C2=A0custom prote= cted path. Just for any accident. 1. add configuration to hdfs-site.xml 2. add a command in dfsadmin for refreshing=C2=A0 was: After Hadoop2.7 root path("/") cannot be deleted for any situration. But li= ke '/tmp','/user','/user/hive/warehouse' and so on, shouldn't be deleted mo= stly. So can we add a configuration, then user can custom their own protect= ed path. Just for any accident. 1. add configuration to hdfs-site.xml 2. add a command in dfsadmin for refreshing=C2=A0 > Support protected path configuration > ------------------------------------ > > Key: HDFS-13037 > URL: https://issues.apache.org/jira/browse/HDFS-13037 > Project: Hadoop HDFS > Issue Type: New Feature > Components: namenode > Reporter: chuanjie.duan > Priority: Major > > After Hadoop2.7 root path("/") cannot be deleted for any situration. But = like '/tmp','/user','/user/hive/warehouse' and so on, shouldn't be deleted = mostly. So can we=C2=A0let user=C2=A0config=C2=A0 their own=C2=A0custom pro= tected path. Just for any accident. > 1. add configuration to hdfs-site.xml > 2. add a command in dfsadmin for refreshing=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org