[
https://issues.apache.org/jira/browse/HDFS-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504576#comment-14504576
]
Jitendra Nath Pandey commented on HDFS-7240:
--------------------------------------------
[~steve_l], thanks for the review.
bq. is there a limit on the #of storage volumes in a cluster? does GET/ return
all of them?
Please see my discussion on limits above. The storage volumes are created by
admins, therefore, are not expected to be too many.
bq. any way to enum users? e.g. GET /admin/user/ ?
We don't plan to manage users in ozone. In this respect we deviate from
popular public object stores. This is because, in a private cluster deployment
the user management is usually tied to corporate user accounts. Instead we
choose storage volume abstraction for certain administrative settings like
quota. However, admins can choose to allocate a storage volume for each user.
bq. what if I want to GET the 1001st entry in an object store?
Not sure I understand the use case. Do you mean the users would like to
query using some sort of entry number or index?
bq. GET on object must support ranges
Agree, we plan to take up this feature in the 2nd phase.
bq. HEAD should supply content-length
This should be easily doable. We will keep it in mind for container
implementation.
> Object store in HDFS
> --------------------
>
> Key: HDFS-7240
> URL: https://issues.apache.org/jira/browse/HDFS-7240
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Jitendra Nath Pandey
> Assignee: Jitendra Nath Pandey
> Attachments: Ozone-architecture-v1.pdf
>
>
> This jira proposes to add object store capabilities into HDFS.
> As part of the federation work (HDFS-1052) we separated block storage as a
> generic storage layer. Using the Block Pool abstraction, new kinds of
> namespaces can be built on top of the storage layer i.e. datanodes.
> In this jira I will explore building an object store using the datanode
> storage, but independent of namespace metadata.
> I will soon update with a detailed design document.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
