You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Charles Lamb (JIRA)" <ji...@apache.org> on 2015/01/08 18:45:36 UTC
[jira] [Commented] (HDFS-7568) Support immutability
(Write-once-read-many) in HDFS
[ https://issues.apache.org/jira/browse/HDFS-7568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269735#comment-14269735 ]
Charles Lamb commented on HDFS-7568:
------------------------------------
Hi [~sureshms],
Thanks for getting this started. It's a good feature to add.
You may want to add 'creating an encryption zone' to the list of operations that are prohibited when a directory is set to be immutable, as well as define whether or not it is allowed on an 'Immutable with append' directory. In some sense it's implied in your current list because you specify that extended attributes can not be set or removed and that's a large part of what EZ creation is about. But recall that all EZs' xattrs are part of the special 'raw.*' namespace which gets special treatment in the xattr world. I could see EZ creation as an operation that is prohibited for 'Immutable' directories, but allowed in 'Immutable with append' directories since subdir creation is allowed. In any case, it should probably be spelled out.
Does /.reserved/raw get any special treatment in an immutable directory?
Charles
> Support immutability (Write-once-read-many) in HDFS
> ---------------------------------------------------
>
> Key: HDFS-7568
> URL: https://issues.apache.org/jira/browse/HDFS-7568
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: namenode
> Affects Versions: 2.7.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
>
> Many regulatory compliance requires storage to support WORM functionality to protect sensitive data from being modified or deleted. This jira proposes adding that feature to HDFS.
> See the following comment for more description.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)