[
https://issues.apache.org/jira/browse/HDFS-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15293822#comment-15293822
]
Colin Patrick McCabe commented on HDFS-7240:
--------------------------------------------
bq. Another question about reading the ApacheCon slides: the question "Why an
Object Store" was well answered. How about "why an object store as part of
HDFS"? IIUC Ozone is only leveraging a very small portion of HDFS code. Why
should it be a part of HDFS instead of a separate project?
That's a very good question. Why can't ozone be its own subproject within
Hadoop? We could add a hadoop-ozone directory at the top level of the git
repo. Ozone seems to be reusing very little of the HDFS code. For example, it
doesn't store blocks the way the DataNode stores blocks. It doesn't run the
HDFS NameNode. It doesn't use the HDFS client code.
> 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, ozone_user_v0.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
