[
https://issues.apache.org/jira/browse/HDFS-6847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098197#comment-14098197
]
Jing Zhao commented on HDFS-6847:
---------------------------------
Yeah, actually I tried to put setStoragePolicyID to INode. However, since we
currently use XAttr for setting the storage policy id, and
FSDirectory#setINodeXAttrs now contains both setting and checking logic, it is
not easy to find a clean way to move setStoragePolicyID into INode. Maybe we
can use separate jiras to do this code cleanup?
> Archival Storage: Support storage policy on directories
> -------------------------------------------------------
>
> Key: HDFS-6847
> URL: https://issues.apache.org/jira/browse/HDFS-6847
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer, namenode
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-6847.000.patch, HDFS-6847.001.patch
>
>
> This jira plans to add storage policy support on directory, i.e., users can
> set/get storage policy for not only files but also directories.
> We allow users to set storage policies for nested directories/files. For a
> specific file/directory, its storage policy then should be its own storage
> policy, if it is specified, or the storage policy specified on its nearest
> ancestral directory. E.g., for a path /foo/bar/baz, if two different policies
> are set on foo and bar (p1 for foo and p2 for bar), the storage policies for
> baz, bar, and foo should be p2, p2, and p1, respectively.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
