[
https://issues.apache.org/jira/browse/HDFS-15181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-15181:
------------------------------
Description:
HDFS-10756 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-10756 can be remedied quickly, it needs to be reverted.
was:
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.
> 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-10756 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-10756 can be remedied quickly, it needs to be reverted.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
