[
https://issues.apache.org/jira/browse/HDFS-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997202#comment-13997202
]
Tsz Wo Nicholas Sze commented on HDFS-2006:
-------------------------------------------
Thanks [~cnauroth] for showing me the pointer. I will look at the code in more
details.
Although large value is not yet supported in the current phase, the "XAttr with
large value" section in the design doc should mention that if large value is
supported, the large values should not be written to edit log. Otherwise, edit
log will grow very fast.
Also, I think we should have different limits for different XAttr namespaces
(user, trusted, security and system) since we may want to put a smaller limit
for the user visible namespaces. How does it sound?
> ability to support storing extended attributes per file
> -------------------------------------------------------
>
> Key: HDFS-2006
> URL: https://issues.apache.org/jira/browse/HDFS-2006
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: HDFS XAttrs (HDFS-2006)
> Reporter: dhruba borthakur
> Assignee: Yi Liu
> Attachments: HDFS-XAttrs-Design-1.pdf, HDFS-XAttrs-Design-2.pdf,
> HDFS-XAttrs-Design-3.pdf, Test-Plan-for-Extended-Attributes-1.pdf,
> xattrs.1.patch, xattrs.patch
>
>
> It would be nice if HDFS provides a feature to store extended attributes for
> files, similar to the one described here:
> http://en.wikipedia.org/wiki/Extended_file_attributes.
> The challenge is that it has to be done in such a way that a site not using
> this feature does not waste precious memory resources in the namenode.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
