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

Swagat Behera commented on HADOOP-13074:
----------------------------------------

Hi [~cnauroth] you can resolve this issue. The documentation does help but I 
feel if we fail the tests in such cases with an exception stating "Non empty 
bucket found, hence failing the test" would make it more clear.

> TestS3AContractRootDir#testListEmptyRootDirectory fails with 
> java.io.IOException: Root directory operation rejected
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-13074
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13074
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/s3, test
>    Affects Versions: 3.0.0
>            Reporter: Swagat Behera
>
> TestS3AContractRootDir#testListEmptyRootDirectory fails with 
> java.io.IOException: Root directory operation rejected . 
> Following 
> https://github.com/apache/hadoop/blob/trunk/hadoop-tools/hadoop-aws/src/site/markdown/tools/hadoop-aws/index.md,
>  I had inputted a non empty S3 bucket with appropriate keys. 
> This test gets the status under the root and tries to delete all the folders 
> under that iteratively along with the root folder.
> When it tries to delete the root folder, 
> ContractTestUtils::rejectRootOperation() throws "Root directory operation 
> rejected" exception. This is bound to happen since the allowRootOperation 
> flag is not set.
> [~cnauroth]
> Please let me know your comments on this. It seems that this test will always 
> fail until we start using 
> ContractTestUtils::assertDeleted(allowRootOperations=True) .
> + [~fabbri], [~mackrorysd] for FYI



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to