[ 
https://issues.apache.org/jira/browse/HDFS-15154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17042127#comment-17042127
 ] 

Siddharth Wagle edited comment on HDFS-15154 at 2/21/20 7:33 PM:
-----------------------------------------------------------------

Hi [~ayushtkn], thanks for the suggestion, I was just about to upload a new 
version :-)

So, Configuration has a DeprecationContext and it handles deprecation by making 
sure that new config key gets the deprecated config's value after the 
Deprecation is added to the context, and the new key is not in the configs. 
HdfsConfiguration does this by statically loading up a bunch of keys into the 
DeprecationContext, we also get a log warning, etc as a result of this. I 
wanted to make use of this in the new patch.

What I would have liked to do is actually override valueOf in the _enum_ to 
make this even more cleaner and readable but unfortunately Java does not allow 
it.

In the new patch I am verifying that deprecated key work correctly as well, do 
let me know what you think, I wanted to avoid special handling at the call site 
for the deprecation. 


was (Author: swagle):
Hi [~ayushtkn], thanks for the suggestion, I was just about to upload a new 
version :-)

So, Configuration has a DeprecationContext and it handles deprecation by making 
sure that new config key gets the deprecated config's value after the 
Deprecation is added to the context, HdfsConfiguration does this by statically 
loading up a bunch of keys into the DeprecationContext, we also get a log 
warning, etc as a result of this. I wanted to make use of this in the new patch.

What I would have liked to do is actually override valueOf in the _enum_ to 
make this even more cleaner and readable but unfortunately Java does not allow 
it.

In the new patch I am verifying that deprecated key work correctly as well, do 
let me know what you think, I wanted to avoid special handling at the call site 
for the deprecation. 

> Allow only hdfs superusers the ability to assign HDFS storage policies
> ----------------------------------------------------------------------
>
>                 Key: HDFS-15154
>                 URL: https://issues.apache.org/jira/browse/HDFS-15154
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>    Affects Versions: 3.0.0
>            Reporter: Bob Cauthen
>            Assignee: Siddharth Wagle
>            Priority: Major
>         Attachments: HDFS-15154.01.patch, HDFS-15154.02.patch, 
> HDFS-15154.03.patch, HDFS-15154.04.patch, HDFS-15154.05.patch
>
>
> Please provide a way to limit only HDFS superusers the ability to assign HDFS 
> Storage Policies to HDFS directories.
> Currently, and based on Jira HDFS-7093, all storage policies can be disabled 
> cluster wide by setting the following:
> dfs.storage.policy.enabled to false
> But we need a way to allow only HDFS superusers the ability to assign an HDFS 
> Storage Policy to an HDFS directory.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to