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

Steve Loughran updated HADOOP-13188:
------------------------------------
    Attachment: HADOOP-13188-branch-2-001.patch

Patch 001

# removed the overidden test case which was skipping the contract test
# verified that the base test failed
# patched S3AFileSystem to check for dest being a dir
# verified that with that change, the test passes

Full test run completed against S3 Ireland

{code}

Tests run: 225, Failures: 0, Errors: 0, Skipped: 5

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17:24 min
[INFO] Finished at: 2016-05-24T15:02:47+01:00
[INFO] Final Memory: 17M/284M
[INFO] ------------------------------------------------------------------------
{code}

> S3A file-create should throw error rather than overwrite directories
> --------------------------------------------------------------------
>
>                 Key: HADOOP-13188
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13188
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>    Affects Versions: 2.7.2
>            Reporter: Raymie Stata
>            Priority: Minor
>         Attachments: HADOOP-13188-branch-2-001.patch
>
>
> S3A.create(Path,FsPermission,boolean,int,short,long,Progressable) is not 
> checking to see if it's being asked to overwrite a directory.  It could 
> easily do so, and should throw an error in this case.
> There is a test-case for this in AbstractFSContractTestBase, but it's being 
> skipped because S3A is a blobstore.  However, both the Azure and Swift file 
> systems make this test, and the new S3 one should as well.



--
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