[
https://issues.apache.org/jira/browse/HDDS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646289#comment-16646289
]
LiXin Ge commented on HDDS-519:
-------------------------------
Test in my local, seems work well in the nomal case, but I'm not sure whether
should we throw the exception xml when operate in a volume that doesn't exist.
{noformat}
[root@EC130 bin]# curl -X GET http://127.0.0.1:9878/bad
<?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>NoSuchVolume</Code>
<Message>The specified volume does not exist</Message>
<Resource>Volume</Resource>
<RequestId>27b329eb-66c8-4685-b002-ed57a35dbbc0</RequestId>
</Error>
{noformat}
> 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]
