[
https://issues.apache.org/jira/browse/HADOOP-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653305#action_12653305
]
Tom White commented on HADOOP-3497:
-----------------------------------
Successfully ran the unit tests and test-patch
{noformat}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 6 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath
integrity.
{noformat}
> 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
> Assignee: Tom White
> Fix For: 0.20.0
>
> Attachments: hadoop-3497-test.patch, hadoop-3497-v2.patch,
> hadoop-3497-v3.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.
