[
https://issues.apache.org/jira/browse/HDFS-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15204943#comment-15204943
]
Virajith Jalaparti commented on HDFS-9809:
------------------------------------------
Hi [~zhz], Thanks for the comment.
One concrete example where a different sub-class of {{ReplicaInfo}} might be
used is Ozone (HDFS-7240) where the replica can be stored in the underlying
key-value store. Similar to the {{DatasetSpi}}/{{FsDatasetSpi}}, we could have
{{ReplicaInfo}}/{{FsReplicaInfo}}. We are still going over the changes proposed
by HDFS-7240 and in the process of understanding if a different sub-class of
{{ReplicaInfo}} makes sense there.
We are currently working on the design document for HDFS-9806 and will post it
soon (within the week). If it ends up being the case that this work is useful
only in the context of HDFS-9806, we will make it a subtask.
> Abstract implementation-specific details from the datanode
> ----------------------------------------------------------
>
> Key: HDFS-9809
> URL: https://issues.apache.org/jira/browse/HDFS-9809
> Project: Hadoop HDFS
> Issue Type: Task
> Reporter: Virajith Jalaparti
> Assignee: Virajith Jalaparti
> Attachments: HDFS-9809.001.patch
>
>
> Multiple parts of the Datanode (FsVolumeSpi, ReplicaInfo, FSVolumeImpl etc.)
> implicitly assume that blocks are stored in java.io.File(s) and that volumes
> are divided into directories. We propose to abstract these details, which
> would help in supporting other storages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
