[
https://issues.apache.org/jira/browse/HADOOP-8709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13437925#comment-13437925
]
Jason Lowe commented on HADOOP-8709:
------------------------------------
I originally thought the change was unintentional until I ran across the
explicit test cases for it in FSMainOperationsBaseTest and
FileContextMainOperationsBaseTest. That indicates we intentionally want
globStatus to throwing FNFE.
I agree that if we're serious about preserving backwards compatibility, we need
to start creating alternative methods with the new behavior rather than
breaking the contracts of established methods. And I, too, am skeptical on the
merits of having globStatus break compatibility to throw FNFE.
> 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
