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

Steve Watt commented on HADOOP-9984:
------------------------------------

To the best of my knowledge, we have 8 out-of-tree Hadoop FileSystem 
implementations that might be affected by this (CassandraFS, CephFS, CleverSafe 
Object Store, GlusterFS, MapR FileSystem, Quantcast File System, Symtantec 
Veritas Cluster File System and GridGain) and 2 in-tree (S3,Swift). Both 9984 
and 9972 just popped up on my radar, would it be possible to give the glusterfs 
community until next wednesday (October 9th) to properly digest this and 
comment appropriately? 

Also, speaking for the glusterfs project, we don't create a glusterfs Hadoop 
FileSystem plugin for specific versions of Hadoop. Due to the way the Hadoop FS 
interface is designed now, we can create a single Hadoop 2.x plugin for 
glusterfs that is backwards compatible, so we just have one.

> FileSystem#globStatus and FileSystem#listStatus should resolve symlinks by 
> default
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-9984
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9984
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 2.1.0-beta
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>            Priority: Blocker
>         Attachments: HADOOP-9984.001.patch, HADOOP-9984.003.patch, 
> HADOOP-9984.005.patch, HADOOP-9984.007.patch, HADOOP-9984.009.patch, 
> HADOOP-9984.010.patch, HADOOP-9984.011.patch, HADOOP-9984.012.patch, 
> HADOOP-9984.013.patch, HADOOP-9984.014.patch
>
>
> During the process of adding symlink support to FileSystem, we realized that 
> many existing HDFS clients would be broken by listStatus and globStatus 
> returning symlinks.  One example is applications that assume that 
> !FileStatus#isFile implies that the inode is a directory.  As we discussed in 
> HADOOP-9972 and HADOOP-9912, we should default these APIs to returning 
> resolved paths.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to