hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nanda kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-705) OS3Exception resource name should be the actual resource name
Date Mon, 22 Oct 2018 10:08:00 GMT

    [ https://issues.apache.org/jira/browse/HDDS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658810#comment-16658810
] 

Nanda kumar commented on HDDS-705:
----------------------------------

[~shashikant], thanks for the update. I will revet the existing commit and re-commit this
without HDDS-676 changes.

> 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
>         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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message