hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13343) globStatus returns null for file path that exists but is filtered
Date Mon, 11 Jul 2016 10:56:11 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15370552#comment-15370552

Steve Loughran commented on HADOOP-13343:

This sounds like your opportunity to define what globStatus is meant to do as part of HADOOP-12177
; I've looked at it when doing HADOOP-13207, but decided I was scared.

We really need written down what globStatus is meant to do 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
> 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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message