Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-15620 Über-jira: S3A phase VI: Hadoop 3.3 features
  3. HADOOP-16420

S3A returns 400 "bad request" on a single path within an S3 bucket

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 3.3.0
    • Fix Version/s: None
    • Component/s: fs/s3
    • Labels:
      None

      Description

      Filing this as "who knows?"; surfaced during testing. Notable that the previous testing was playing with SSE-C, if that makes a difference: it could be that there's a marker entry encrypted with SSE-C that is now being rejected by a different run.

      Somehow, with a set of credentials I can work with all paths in a directory, except read the dir marker /fork-0001/"; try that and a 400 bad request comes back. AWS console views the path as an empty dir.

        Attachments

        1. out.txt
          14 kB
          Steve Loughran

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              stevel@apache.org Steve Loughran
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: