Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-15181

Webhdfs getTrashRoot() causes internal AccessControlException

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Duplicate
    • None
    • None
    • webhdfs
    • None

    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.

      Attachments

        1. HDFS-15181.trunk.patch
          3 kB
          Kihwal Lee

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kihwal Kihwal Lee
            kihwal Kihwal Lee
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment