You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2019/07/10 18:43:00 UTC

[jira] [Created] (HADOOP-16420) S3A returns 400 "bad request" on a single path within an S3 bucket

Steve Loughran created HADOOP-16420:
---------------------------------------

             Summary: S3A returns 400 "bad request" on a single path within an S3 bucket
                 Key: HADOOP-16420
                 URL: https://issues.apache.org/jira/browse/HADOOP-16420
             Project: Hadoop Common
          Issue Type: Sub-task
          Components: fs/s3
    Affects Versions: 3.3.0
            Reporter: Steve Loughran


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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org