Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 3 Sep 2013 19:31:52 +0000 (UTC)
From: "Daryn Sharp (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12665999.1377722451558.73049.1378236712864@arcas>
In-Reply-To: <JIRA.12665999.1377722451558@arcas>
References: <JIRA.12665999.1377722451558@arcas>
Subject: [jira] [Commented] (HADOOP-9912) globStatus of a symlink to a
 directory does not report symlink as a directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daryn Sharp commented on HADOOP-9912:
-------------------------------------

bq.  The shell needs to be able to "see" symlinks, not just the files they point to

This is why I proposed we return the resolved stat with the symlink bit set.  Symlink-aware code, like the shell's ls can call getFileLinkStatus if they need to.  Like users, the rest of the shell's commands probably won't care about symlinks either.

Adding a flag for {{globStatus}} will fix the specific case observed by pig, but the same issue still applies for any user code that calls {{listStatus}}.  We probably need for both to have a flag.


> globStatus of a symlink to a directory does not report symlink as a directory
> -----------------------------------------------------------------------------
>
>                 Key: HADOOP-9912
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9912
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.3.0
>            Reporter: Jason Lowe
>            Priority: Blocker
>         Attachments: HADOOP-9912-testcase.patch
>
>
> globStatus for a path that is a symlink to a directory used to report the resulting FileStatus as a directory but recently this has changed.

--
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