[
https://issues.apache.org/jira/browse/HADOOP-12501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969436#comment-14969436
]
Chen He commented on HADOOP-12501:
----------------------------------
Hi [~steve_l], thank you for the reply. Swift server has its own access control
mechanism in the backend. However, it may not satisfy the needs in some cases.
For example:
Current storage provider sells a service to a company A, the A has several
types of users: admin, general user, etc. If the admin wants to backup or
restore all files on HDFS to swift object store, the u/g/p data may lost if the
admin uses 'distcp' to copy files (it is also possible that admin copies data
blocks and metadata instead of using 'distcp', then there is no need to
preserve u/g/p). All u/g/p will disappear. My thought was to preserve the u/g/p
into somewhere in the metadata of each object, then, it will avoid a lot of
work for the admin to recover u/g/p in this case.
> 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)
