[
https://issues.apache.org/jira/browse/HADOOP-9652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880487#comment-13880487
]
Jason Lowe commented on HADOOP-9652:
------------------------------------
+1, thanks Andrew! I plan on committing this but need to clear up something
about the state of this JIRA. It looks like the reported problem will still
exist, since getFileLinkStatus will not fill in the link owner and mode by
default after the workaround patch. In that sense the cleanest thing would be
to simply revert and commit a real fix later, but it looks like the last
committed patch did more than just fix the described problem (e.g.: also fixing
HADOOP-9693). So I'm thinking we need to rename this JIRA to reflect it's
laying the groundwork for the eventual fix and file a followup JIRA to track
completing the fix. Does that make sense?
> 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: Colin Patrick McCabe
> Fix For: 2.4.0
>
> Attachments: 0001-temporarily-disable-HADOOP-9652.patch,
> hadoop-9452-1.patch, hadoop-9652-2.patch, hadoop-9652-3.patch,
> hadoop-9652-4.patch, hadoop-9652-5.patch, hadoop-9652-6.patch,
> hadoop-9652-workaround.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 was sent by Atlassian JIRA
(v6.1.5#6160)
