[
https://issues.apache.org/jira/browse/HDFS-7240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300488#comment-15300488
]
Andrew Wang commented on HDFS-7240:
-----------------------------------
Quoting my earlier response to Anu:
bq. Really though, even if the community hadn't explicitly expressed interest,
all of this activity should still have been done in a public forum. It's very
hard for newcomers to ramp up unless design discussions are being done publicly.
TDevelopment is supposed to be done in the open so everyone can watch and
contribute.
Also, code is not the only form of contribution. As also mentioned above, we
had a call in late February this year, which is where we discussed the need for
range partitioning (something I'm glad is being done in the new design) as well
as raising concerns about the number of hops to lookup and read data (which I'm
guessing is why metadata is now replicated via Raft rather than stored in
containers).
> 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: Andrew Wang
> 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
