[
https://issues.apache.org/jira/browse/HADOOP-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371655#comment-15371655
]
Colin P. McCabe commented on HADOOP-13343:
------------------------------------------
bq. This makes it impossible for the caller to discern the difference between
the file not existing at all vs. being suppressed by the filter and is
inconsistent with the way it handles globs for an existing dir but fail to
match anything within the dir.
Sorry if this is a nitpick, but it's not impossible for the code to know that
the filter is suppressing the file entry. The filter object could set a
boolean when it's asked to examine an entry, and the code could check this
entry.
With that being said, maybe there is case for (re)adopting the behavior
proposed here.
> globStatus returns null for file path that exists but is filtered
> -----------------------------------------------------------------
>
> Key: HADOOP-13343
> URL: https://issues.apache.org/jira/browse/HADOOP-13343
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.7.2
> Reporter: Jason Lowe
> Priority: Minor
> Attachments: HADOOP-13343.001.patch
>
>
> If a file path without globs is passed to globStatus and the file exists but
> the specified input filter suppresses it then globStatus will return null
> instead of an empty array. This makes it impossible for the caller to
> discern the difference between the file not existing at all vs. being
> suppressed by the filter and is inconsistent with the way it handles globs
> for an existing dir but fail to match anything within the dir.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
