[ https://issues.apache.org/jira/browse/HADOOP-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474267#comment-13474267 ]
Jason Lowe commented on HADOOP-8906: ------------------------------------ bq. In essence, perhaps a user filter means the query is always a glob? I can see it going either way. Yes, I thought about that as well. Maybe it would be more consistent to return empty instead of null in that case, but I was erring on the side of caution to maintain compatibility with the previous version's behavior. It all comes down to what a result of null really means. If it's being used to check for globs in the path then arguably we should continue to return null because someone could be using/abusing globStatus(path, falseFilter) to check for globs in a path even if the path exists in the filesystem. > 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