[
https://issues.apache.org/jira/browse/HDFS-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109589#comment-15109589
]
Arpit Agarwal commented on HDFS-9534:
-------------------------------------
bq. I had been thinking that the remove operation applies just to the specific
named inode, and it would not directly alter anything lower in the tree. (Of
course, it's possible that removing the storage policy from an inode causes its
children to start inheriting different storage policy settings from higher in
the tree.)
Yes I had the same assumption. An unspecified storage policy would result in
checking policies on ancestors. We should add a couple of unit tests for nested
policy removal.
Also it's better to call it {{resetStoragePolicy}} or {{clearStoragePolicy}}
rather than {{removeStoragePolicy}}. That makes it explicit the operation is
idempotent.
> Add CLI command to clear storage policy from a path.
> ----------------------------------------------------
>
> Key: HDFS-9534
> URL: https://issues.apache.org/jira/browse/HDFS-9534
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: tools
> Reporter: Chris Nauroth
> Assignee: Xiaobing Zhou
> Attachments: HDFS-9534.001.patch
>
>
> The {{hdfs storagepolicies}} command has sub-commands for
> {{-setStoragePolicy}} and {{-getStoragePolicy}} on a path. However, there is
> no {{-removeStoragePolicy}} to remove a previously set storage policy on a
> path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
