[
https://issues.apache.org/jira/browse/HDFS-15091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008034#comment-17008034
]
Hudson commented on HDFS-15091:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17811 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17811/])
HDFS-15091. Cache Admin and Quota Commands Should Check SuperUser Before
(ayushsaxena: rev f8644fbe9f76fb2990bcc997a346649e4d432d91)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirAttrOp.java
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNDNCacheOp.java
> Cache Admin and Quota Commands Should Check SuperUser Before Taking Lock
> ------------------------------------------------------------------------
>
> Key: HDFS-15091
> URL: https://issues.apache.org/jira/browse/HDFS-15091
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-15091-01.patch, HDFS-15091-02.patch
>
>
> As of now all API check superuser before taking lock, Similarly can be done
> for the cache commands and setQuota.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
