[
https://issues.apache.org/jira/browse/HDFS-13037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chuanjie.duan updated HDFS-13037:
---------------------------------
Description:
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 let user config their own custom protected path. Just for any
accident.
1. add configuration to hdfs-site.xml
2. add a command in dfsadmin for refreshing
was:
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 add a configuration, then user can custom their own protected path.
Just for any accident.
1. add configuration to hdfs-site.xml
2. add a command in dfsadmin for refreshing
> 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 let user config their own custom protected path. Just for any
> accident.
> 1. add configuration to hdfs-site.xml
> 2. add a command in dfsadmin for refreshing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
