[
https://issues.apache.org/jira/browse/HDFS-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001552#comment-14001552
]
Uma Maheswara Rao G commented on HDFS-2006:
-------------------------------------------
Hi [~kihwal], You flagged this issue as incompatible with respective to dot
release I guess right?
If I am correct, with NNLayoutVersion changes, we can not do downgrade, but we
can do only rollback and newly added data will loss. As NNLayoutVersion change
does not support downgrade, and dot releases can not break this and we should
not port this to 2.4.X releases. Is this the reason to set this as Incompatible
change?
I think we don't intend to port this to 2.4.x releases. This will go into next
minor release only if we could make the distCp support by that time. Please
clarify if there is other meaning here.
Thanks Kihwal for keeping an eye on this issue.
> 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: ExtendedAttributes.html, HDFS-2006-Merge-1.patch,
> HDFS-2006-Merge-2.patch, 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)
