Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 1 Feb 2013 17:02:12 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12629971.1359573467416.230057.1359738132895@arcas>
In-Reply-To: <JIRA.12629971.1359573467416@arcas>
References: <JIRA.12629971.1359573467416@arcas>
Subject: [jira] [Commented] (HADOOP-9265) S3 blockstore filesystem breaks
 part of the Filesystem contract
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Nauroth commented on HADOOP-9265:
---------------------------------------

+1 for the new patch

I repeated the tests and they passed.

Just to clarify, I was not objecting to the prior patch.  I just wanted to mention the error handling issue for consideration, and Steve made some good points to justify the behavior.

                
> S3 blockstore filesystem breaks part of the Filesystem contract
> ---------------------------------------------------------------
>
>                 Key: HADOOP-9265
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9265
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3
>    Affects Versions: 1.1.1, 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Tom White
>         Attachments: HADOOP-9265.patch, HADOOP-9265.patch
>
>
> The extended tests of HADOOP-9258 show that s3 is failing things which we always expected an FS to do
> # {{getFileStatus("/")}} to return a {{FileStatus}} -currently it returns a {{FileNotFoundException}}.
> # {{rename("somedir","somedir/childdir")}} to fail. currently it returns true after deleting all the data in {{somedir/}}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira