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

FileContext.createSymlink with kerberos enabled sets wrong owner

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.22.0
    • 0.22.0, 0.23.0
    • None
    • None
    • Kerberos enabled on cluster

    • Reviewed

    Description

      TEST SETUP
      Using attached sample hdfs java program that illustrates the issue.
      Using cluster with Kerberos enabled on cluster

      1. Compile instructions
        $ javac Symlink.java -cp `hadoop classpath`
        $ jar -cfe Symlink.jar Symlink Symlink.class
      1. create test file for symlink to use
        1. hadoop fs -touchz /user/username/filetest
      1. Create symlink using file context
        2. hadoop jar Symlink.jar ln /user/username/filetest /user/username/testsymlink
      1. Verify owner of test file
        3. hadoop jar Symlink.jar ls /user/username/
        rw-rr- username hdfs /user/jeagles/filetest
        -rwxrwxrwx username@XX.XXXX.XXXXX.XXX hdfs /user/username/testsymlink

      RESULTS
      1. Owner shows 'username@XX.XXXX.XXXXX.XXX' for symlink, expecting 'username'.
      2. Symlink is corrupted and can't removed, since it was created with an invalid user

      ------------------------
      Sample program to create Symlink

      FileContext fc = FileContext.getFileContext(getConf());
      fc.createSymlink(target, symlink, false);

      ---------------------------------------

      Attachments

        1. HDFS-1821-2.patch
          2 kB
          John George
        2. HDFS-1821.patch
          2 kB
          John George

        Activity

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

          People

            johnvijoe John George
            johnvijoe John George
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment