hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13309) Document S3A known limitations in file ownership and permission model.
Date Wed, 22 Jun 2016 16:04:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344619#comment-15344619
] 

Chris Nauroth commented on HADOOP-13309:
----------------------------------------

bq. In HADOOP-12774 I proposed making the owner UGI.getShortName(), that way in code running
as a different user, you'd pick up the relevant user.

This is the same implementation choice that Azure Data Lake used recently in HADOOP-12666.
 Maybe it makes sense for the file system spec to state that file systems without support
for ownership must fall back to UGI?  Then, the limitation would at least be the same limitation
across alternative file systems.

> Document S3A known limitations in file ownership and permission model.
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-13309
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13309
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Chris Nauroth
>            Priority: Minor
>
> S3A does not match the implementation of HDFS in its handling of file ownership and permissions.
 Fundamental S3 limitations prevent it.  This is a frequent source of confusion for end users.
 This issue proposes to document these known limitations.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message