hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjay Radia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-8709) globStatus changed behavior from 0.20/1.x
Date Wed, 22 Aug 2012 23:24:43 GMT

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

Sanjay Radia commented on HADOOP-8709:
--------------------------------------

Daryn, there are two areas of consistency:
# /a/nonExist/c and /a/nonExist*/c - your argument above - consistency when parent dir is
missing
# /a/nonExist*/c and /a/nonExist/c* - consistency for globing regardless of where it occurs
- return empty or the set that matches.
I prefer the 2nd one.

                
> 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

        

Mime
View raw message