You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Kihwal Lee (Jira)" <ji...@apache.org> on 2020/02/18 18:14:00 UTC

[jira] [Updated] (HDFS-15181) Webhdfs getTrashRoot() causes internal AccessControlException

     [ https://issues.apache.org/jira/browse/HDFS-15181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee updated HDFS-15181:
------------------------------
    Summary: Webhdfs getTrashRoot() causes internal AccessControlException  (was: Webhdfs getTrashRoot() caused internal AccessControlException)

> Webhdfs getTrashRoot() causes internal AccessControlException
> -------------------------------------------------------------
>
>                 Key: HDFS-15181
>                 URL: https://issues.apache.org/jira/browse/HDFS-15181
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>            Reporter: Kihwal Lee
>            Priority: Blocker
>
> HDFS-10883 added the {{getTrashRoot()}} support for WebHdfs. However, it was done by creating a FileSystem instance in the namenode. This is unacceptable for many reasons and also the implementation is not correct.  The current implementation only works when security is off. When security is on, the internal client received AccessControlException and does not work.
> A similar bug was preset in HDFS-11156. Again, this is not merely a "performance bug".  These don't work with security on.  Fortunately HDFS-11156 was reverted and reworked.  I've recently reverted it and ported the rework to branch-2.10.
> Unless HDFS-10883 can be remedied quickly, it needs to be reverted.



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

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