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

Colin Patrick McCabe commented on HADOOP-9652:
----------------------------------------------

OK.  I have reverted the patch.

Here is a summary of the issues we know of with the original patch:
* Fallback path should handle MacOS (HADOOP-9783)
* Issue with URI fragment handling and DistCp (MAPREDUCE-5430)
* Stray {{System.println}} caused some TestDFSShell failures
* must not use "{{bash -c}}"

So we need a new version of the patch which addresses all of these.  
Additionally, can you touch a file in each project (i.e., hadoop-hdfs-project, 
hadoop-mapreduce-project, hadoop-yarn-project), so that we get the full Jenkins 
run, rather than just a Jenkins run on common?
                
> RawLocalFs#getFileLinkStatus does not fill in the link owner and mode
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-9652
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9652
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Colin Patrick McCabe
>            Assignee: Andrew Wang
>             Fix For: 2.3.0
>
>         Attachments: hadoop-9452-1.patch, hadoop-9652-2.patch, 
> hadoop-9652-3.patch
>
>
> {{RawLocalFs#getFileLinkStatus}} does not actually get the owner and mode of 
> the symlink, but instead uses the owner and mode of the symlink target.  If 
> the target can't be found, it fills in bogus values (the empty string and 
> FsPermission.getDefault) for these.
> Symlinks have an owner distinct from the owner of the target they point to, 
> and getFileLinkStatus ought to expose this.
> In some operating systems, symlinks can have a permission other than 0777.  
> We ought to expose this in RawLocalFilesystem and other places, although we 
> don't necessarily have to support this behavior in HDFS.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to