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

Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2024/12/03 13:40:02 UTC

[jira] [Updated] (HADOOP-16571) s3a to improve diags on s3a bad request message

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

Steve Loughran updated HADOOP-16571:
------------------------------------
    Parent: HADOOP-19353  (was: HADOOP-18477)

> s3a to improve diags on s3a bad request message
> -----------------------------------------------
>
>                 Key: HADOOP-16571
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16571
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>            Priority: Minor
>
> if you have the endpoint or signing algorithm wrong, your first sign of trouble on an s3a FS operation is a 400 bad request during init.
> Proposed: include those properties on failure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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