Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11694 Über-jira: S3a phase II: robustness, scale and performance
  3. HADOOP-13188

S3A file-create should throw error rather than overwrite directories

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersConvert to IssueMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.7.2
    • 2.8.0, 3.0.0-alpha1
    • fs/s3
    • None

    Description

      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.

      Attachments

        Issue Links

        relates to

        Sub-task - The sub-task of the issue HADOOP-13221 s3a create() doesn't check for an ancestor path being a file

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            stevel@apache.org Steve Loughran Assign to me
            raymie Raymie Stata
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment