[
https://issues.apache.org/jira/browse/HDDS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659215#comment-16659215
]
Hudson commented on HDDS-705:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15285 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15285/])
HDDS-705. addendum patch to fix find bug issue. Contributed by Bharat (bharat:
rev f6498af0d7618c580ecfbc77aff9946362efe4f3)
* (edit)
hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/exception/S3ErrorTable.java
* (edit)
hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/endpoint/EndpointBase.java
> OS3Exception resource name should be the actual resource name
> -------------------------------------------------------------
>
> Key: HDDS-705
> URL: https://issues.apache.org/jira/browse/HDDS-705
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Fix For: 0.3.0, 0.4.0
>
> Attachments: HDDS-705.00.patch
>
>
> [https://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html]
> {code:java}
> <?xml version="1.0" encoding="UTF-8"?>
> <Error>
> <Code>NoSuchKey</Code>
> <Message>The resource you requested does not exist</Message>
> <Resource>/mybucket/myfoto.jpg</Resource>
> <RequestId>4442587FB7D0A2F9</RequestId>
> </Error>{code}
>
> Right now in the code we are print resource as "bucket" , "key" instead of
> actual resource name.
>
> Documentation shows key name with bucket, but actually when tried on AWS S3
> endpoint it shows just key name, found this information when using mitmproxy.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
