hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3497) File globbing with a PathFilter is too restrictive
Date Wed, 13 Aug 2008 12:54:46 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tom White updated HADOOP-3497:
------------------------------

    Release Note: Changed the semantics of file globbing with a PathFilter (using the globStatus
method of FileSystem). Previously, the filtering was too restrictive, so that a glob of /*/*
and a filter that only accepts /a/b would not have matched /a/b. With this change /a/b does
match. 
    Hadoop Flags: [Incompatible change]

> File globbing with a PathFilter is too restrictive
> --------------------------------------------------
>
>                 Key: HADOOP-3497
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3497
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs
>    Affects Versions: 0.17.0
>            Reporter: Tom White
>         Attachments: hadoop-3497-test.patch, hadoop-3497.patch
>
>
> Consider the file hierarchy
> {noformat}
> /a
> /a/b
> {noformat}
> Calling the globStatus method on FileSystem with a path of {noformat}/*/*{noformat} and
a PathFilter that only accepts {{/a/b}} returns no matches. It should return a single match:
{{/a/b}}.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message