You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2015/01/16 14:32:35 UTC

[jira] [Resolved] (HADOOP-4436) S3 object names with arbitrary slashes confuse NativeS3FileSystem

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

Steve Loughran resolved HADOOP-4436.
------------------------------------
       Resolution: Won't Fix
    Fix Version/s: 2.7.0

closing as WONTFIX...s3n, s3a and openstack clients all assume that a "/" paths represent directory delimiters in paths, an assumption that goes pretty deep. Sorry

> S3 object names with arbitrary slashes confuse NativeS3FileSystem
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>             Fix For: 2.7.0
>
>
> Consider a bucket with the following object names:
> * /
> * /foo
> * foo//bar
> NativeS3FileSystem treats an object named "/" as a directory.  Doing an "fs -lsr" causes an infinite loop.
> I suggest we change NativeS3FileSystem to handle these by ignoring any such "invalid" names.  Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)