You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "David Phillips (JIRA)" <ji...@apache.org> on 2008/10/17 03:06:44 UTC

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

S3 object names with arbitrary slashes confuse NativeS3FileSystem
-----------------------------------------------------------------

                 Key: HADOOP-4436
                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
             Project: Hadoop Core
          Issue Type: Bug
            Reporter: David Phillips


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "David Phillips (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Phillips updated HADOOP-4436:
-----------------------------------

    Affects Version/s: 0.18.1

> S3 object names with arbitrary slashes confuse NativeS3FileSystem
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "David Phillips (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641667#action_12641667 ] 

David Phillips commented on HADOOP-4436:
----------------------------------------

I only noticed this with existing buckets written by other tools.

> S3 object names with arbitrary slashes confuse NativeS3FileSystem
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "David Phillips (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Phillips updated HADOOP-4436:
-----------------------------------

    Component/s: fs/s3

> S3 object names with arbitrary slashes confuse NativeS3FileSystem
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Posted by "Tom White (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-4436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641568#action_12641568 ] 

Tom White commented on HADOOP-4436:
-----------------------------------

Is this only a problem for S3 files that are written using other tools, or can you cause this problem by writing using NativeS3FileSystem? The discussion in HADOOP-3257 may be relevant here too. 

> S3 object names with arbitrary slashes confuse NativeS3FileSystem
> -----------------------------------------------------------------
>
>                 Key: HADOOP-4436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4436
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 0.18.1
>            Reporter: David Phillips
>
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.