[
https://issues.apache.org/jira/browse/HADOOP-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474256#comment-13474256
]
Daryn Sharp commented on HADOOP-8906:
-------------------------------------
Yes, I had that case but somehow accidentally removed in the final patch.
The case of a non-glob path with a user-supplied filter is an interesting one.
"null" means the path isn't a glob AND doesn't exist. When an existing
non-glob path is removed by the filter, then arguably maybe it should return
empty array since it's not that the path doesn't exist but that the filter had
no matches. In essence, perhaps a user filter means the query is always a
glob? I can see it going either way.
> paths with multiple globs are unreliable
> ----------------------------------------
>
> Key: HADOOP-8906
> URL: https://issues.apache.org/jira/browse/HADOOP-8906
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Priority: Critical
> Attachments: HADOOP-8906-branch_0.23.patch, HADOOP-8906.patch,
> HADOOP-8906.patch, HADOOP-8906.patch, HADOOP-8906.patch, HADOOP-8906.patch
>
>
> Let's say we have have a structure of "$date/$user/stuff/file". Multiple
> globs are unreliable unless every directory in the structure exists.
> These work:
> date*/user
> date*/user/stuff
> date*/user/stuff/file
> These fail:
> date*/user/*
> date*/user/*/*
> date*/user/stu*
> date*/user/stu*/*
> date*/user/stu*/file
> date*/user/stuff/*
> date*/user/stuff/f*
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
