[HDFS-1821] FileContext.createSymlink with kerberos enabled sets wrong owner

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.22.0
• Fix Version/s: 0.22.0, 0.23.0

Environment

Kerberos enabled on cluster

• Hadoop Flags: Reviewed
• Assignee: John George
• Reporter: John George
• Created: 08/Apr/11 16:20
• Updated: 15/Nov/11 00:52
• Resolved: 14/Apr/11 20:50

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 [e-mail] hdfs /user/username/testsymlink

RESULTS
1. Owner shows '[e-mail]' 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);

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