[
https://issues.apache.org/jira/browse/HADOOP-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438981#comment-13438981
]
Jakob Homan commented on HADOOP-8709:
-------------------------------------
The general consensus of the discussion previously was that returning null
should be avoided (as it requires an extra null check), specifically to
indicate that the file you're looking for wasn't found, since there's a
perfectly good exception to indicate that. The only thing that bothers me
about throwing FNFE for globbing is that globbing is an exploratory operation
and not finding anything, including the base path you were looking at, seems a
reasonable, non-exceptional outcome. If we're going to treat the base path not
existing as something exceptional, FNFE seems a good way to do it.
> 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, 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
