Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-16829 Über-jira: S3A Hadoop 3.3.1 features
  3. HADOOP-16482

S3A doesn't actually verify paths have the correct authority

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • 3.1.0
    • 3.3.0
    • fs/s3
    • None

    Description

      Probably been around a long time, but we've never noticed, assuming that Path.makeQualified(uri, workingDir) did the right thing.

      You can provide any s3a URI to an S3 command and it'll get mapped to the current bucket without any validation that the authorities are equal. Oops.

      Attachments

        Issue Links

          Activity

            People

              stevel@apache.org Steve Loughran
              stevel@apache.org Steve Loughran
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: