hadoop-common-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HADOOP-13343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Colin P. McCabe updated HADOOP-13343:
    Attachment: HADOOP-13343.001.patch

It's easy enough to implement this behavior if you want.  See patch 001.

It seems like the current behavior dates back to at least Hadoop 2.3 though.  It was introduced
by HADOOP-9817.  At this point, changing the behavior to the pre-2.3 behavior may break existing
applications.  Perhaps this is a change we should make in 3.0?

> 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

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

View raw message