[
https://issues.apache.org/jira/browse/HDDS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649322#comment-16649322
]
Elek, Marton commented on HDDS-519:
-----------------------------------
+1. LGTM
Tested with ozones3 cluster and curl, and works well.
Note: I agree, the volume not found exception is not clear, as there is no
volume at s3. One option is to throw bucket not found with custom exception
message but it's not so good. But we need to solve it later. We are just moving
to an other approach where we have no volume in the url and the volume comes
from the username -> volumename naming convention (user elek will use s3elek
volume for all the s3 operation).
Summary: will commit in shortly.
> Implement ListBucket REST endpoint
> ----------------------------------
>
> Key: HDDS-519
> URL: https://issues.apache.org/jira/browse/HDDS-519
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: LiXin Ge
> Priority: Major
> Labels: newbie
> Attachments: HDDS-519.000.patch
>
>
> You can also name it as GetService.
> See te AWS reference:
> https://docs.aws.amazon.com/AmazonS3/latest/API/RESTServiceGET.html
> The List Bucket API needs the call to be handled at the root resource
> (“/{volume}”).
>
> This implementation of the GET operation returns a list of all buckets owned
> by the authenticated sender of the request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
