[
https://issues.apache.org/jira/browse/HADOOP-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974973#comment-14974973
]
Steve Loughran commented on HADOOP-12501:
-----------------------------------------
I see this use case, though I think it's dangerous as people may thing those
permissions may actually apply. There's the other issue that HDFS permissions
are all ACL based; you need to store more than you think.
In unix-land, usually it's left to {{tar}} to do the permissions tracking. I
don't think we quite have the equivalent in HDFS, do we? Maybe you'd want to do
it differently, and have distcp build up an index file, listing every file and
its permissions, which could then be applied to the recovered data. That way,
you'd have a backup story that worked with any back end FS
> Enable SwiftNativeFileSystem to preserve user, group, permission
> ----------------------------------------------------------------
>
> Key: HADOOP-12501
> URL: https://issues.apache.org/jira/browse/HADOOP-12501
> Project: Hadoop Common
> Issue Type: New Feature
> Components: fs/swift
> Affects Versions: 2.7.1
> Reporter: Chen He
> Assignee: Chen He
>
> Currently, if user copy file/dir from localFS or HDFS to swift object store,
> u/g/p will be gone. There should be a way to preserve u/g/p. It will provide
> benefit for a large number of files/dirs transferring between HDFS/localFS
> and Swift object store. We also need to be careful since Hadoop prevent
> general user from changing u/g/p especially if Kerberos is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
