hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7317) Rename StoragePolicy
Date Fri, 31 Oct 2014 21:27:34 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14192520#comment-14192520

Suresh Srinivas commented on HDFS-7317:

I think there is misunderstanding here. Not sure how our discussion led to this. Can you describe
where you see "hard coded mapping to storage policy"?

Btw StoragePolicy today does not map to storage types. It maps *replica placement* across
different storage types. Now one could say that it should have broader goal than just replica
placement (for example whether to erasure code). But that is a different topic than how I
understand this description.

> Rename StoragePolicy
> --------------------
>                 Key: HDFS-7317
>                 URL: https://issues.apache.org/jira/browse/HDFS-7317
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.6.0
>            Reporter: Andrew Wang
> As discussed on HDFS-7285, StoragePolicy might not be the best name for what StoragePolicy
currently is, which is a hardcoded mapping to a StorageType. Ideally the "policy" is what
determines the data temperature in the first place, with the temperature then mapping to the
actual StorageTypes to use.
> There were a number of suggestions presented, e.g. StorageTag, StoragePolicyTag. Let's
figure this out here.

This message was sent by Atlassian JIRA

View raw message