[
https://issues.apache.org/jira/browse/HDFS-8695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643086#comment-14643086
]
Anu Engineer commented on HDFS-8695:
------------------------------------
bq. VolumeHandler#getVolumeInfo requires volume name as parameter. i.e. A URL
/IP:PORT/ozone/volume1?info=service which lists all volume names doesn't look
good.
bq. I feel list of volumes service should be another method which should be
mapped to root path of Ozone as volumes are the top containers of Ozone.
bq. FYI, In S3 the list of the buckets are handled on the root of the resource
path http://docs.aws.amazon.com/AmazonS3/latest/API/RESTServiceGET.html
That is exactly how it is from the protocol perspective. The info=service is
never exposed to user. It is an internal token generated in code. The end user
simply issues GET /. When you get to the point of running code, you will see
that end-users will simply issue GET / and it will return a volumes. In fact
our API is exactly same as AWS for this call.
You should be able to see this and test it out when we have the HTTP handler
code in place.
> OzoneHandler : Add Bucket REST Interface
> ----------------------------------------
>
> Key: HDFS-8695
> URL: https://issues.apache.org/jira/browse/HDFS-8695
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Attachments: hdfs-8695-HDFS-7240.001.patch,
> hdfs-8695-HDFS-7240.002.patch
>
>
> Add Bucket REST interface into Ozone server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
