[ https://issues.apache.org/jira/browse/HADOOP-9877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13761049#comment-13761049 ]
Hudson commented on HADOOP-9877: -------------------------------- FAILURE: Integrated in Hadoop-Mapreduce-trunk #1541 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1541/]) Revert HADOOP-9877 because of breakage reported in HADOOP-9912 (wang: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1520713) * /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/Globber.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/FileContextMainOperationsBaseTest.java * /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/TestFsShellReturnCode.java * /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/fs/TestHDFSFileContextMainOperations.java > Fix listing of snapshot directories in globStatus > ------------------------------------------------- > > Key: HADOOP-9877 > URL: https://issues.apache.org/jira/browse/HADOOP-9877 > Project: Hadoop Common > Issue Type: Bug > Affects Versions: 2.1.0-beta > Reporter: Binglin Chang > Assignee: Binglin Chang > Attachments: HADOOP-9877-branch2.patch, HADOOP-9877.v1.patch, > HADOOP-9877.v2.patch, HADOOP-9877.v3.patch, HADOOP-9877.v4.patch, > HADOOP-9877.v5.patch > > > {code} > decster:~/hadoop> bin/hadoop fs -ls "/foo/.snapshot" > 13/08/16 01:17:22 INFO hdfs.DFSClient: +++++ listPath(/) > 13/08/16 01:17:22 INFO hdfs.DFSClient: +++++ listPath(/foo) > ls: `/foo/.snapshot': No such file or directory > {code} > HADOOP-9817 refactor some globStatus code, but forgot to handle special case > that .snapshot dir is not show up in listStatus but exists, so we need to > explicitly check path existence using getFileStatus, rather than depending on > listStatus results. -- 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