Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 14 Apr 2011 15:21:06 +0000 (UTC)
From: "John George (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <767396540.57882.1302794466157.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <16309532.44060.1302279726839.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-1821) FileContext.createSymlink with
 kerberos enabled sets wrong owner
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019866#comment-13019866 ] 

John George commented on HDFS-1821:
-----------------------------------

     [exec]
     [exec] +1 overall.
     [exec]
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec]
     [exec]     +1 tests included.  The patch appears to include 3 new or modified tests.
     [exec]
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning messages.
     [exec]
     [exec]     +1 javac.  The applied patch does not increase the total number of javac compiler warnings.
     [exec]
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs (version 1.3.9) warnings.
     [exec]
     [exec]     +1 release audit.  The applied patch does not increase the total number of release audit warnings.
     [exec]
     [exec]     +1 system test framework.  The patch passed system test framework compile.
     [exec]


> FileContext.createSymlink with kerberos enabled sets wrong owner
> ----------------------------------------------------------------
>
>                 Key: HDFS-1821
>                 URL: https://issues.apache.org/jira/browse/HDFS-1821
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>         Environment: Kerberos enabled on cluster
>            Reporter: John George
>            Assignee: John George
>         Attachments: HDFS-1821-2.patch, HDFS-1821.patch
>
>
> TEST SETUP
> Using attached sample hdfs java program that illustrates the issue.
> Using cluster with Kerberos enabled on cluster
> # Compile instructions
> $ javac Symlink.java -cp `hadoop classpath`
> $ jar -cfe Symlink.jar Symlink Symlink.class
> # create test file for symlink to use
> 1. hadoop fs -touchz /user/username/filetest
> # Create symlink using file context
> 2. hadoop jar Symlink.jar ln /user/username/filetest /user/username/testsymlink
> # Verify owner of test file
> 3. hadoop jar Symlink.jar ls /user/username/
> -rw-r--r-- 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);
> ---------------------------------------

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira