[ https://issues.apache.org/jira/browse/HADOOP-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437150#comment-13437150 ]
Jason Lowe commented on HADOOP-8709: ------------------------------------ I don't think it's the job of globStatus to be used as a function to distinguish between globbed paths and non-globbed paths based on return code. There's a separate class, GlobFilter, which can be used to check for glob patterns within a path with the added benefit that it doesn't require fs operations. Just discovered that FileContext has duplicated code and therefore the same issues, javadoc inconsistencies and all. > globStatus changed behavior from 0.20/1.x > ----------------------------------------- > > Key: HADOOP-8709 > URL: https://issues.apache.org/jira/browse/HADOOP-8709 > Project: Hadoop Common > Issue Type: Bug > Components: fs > Affects Versions: 0.23.0, 2.0.0-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Priority: Critical > Attachments: HADOOP-8709.patch > > > In 0.20 or 1.x, globStatus will return an empty array if the glob pattern > does not match any files. After HADOOP-6201 it throws FileNotFoundException. > The javadoc states it will return an empty array. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira